and more in a single search tool across platforms. Read the announcement here. |
12/08/2022 12:16 PM
Our organization currently uses SSO to access Saviynt and we have created test user accounts that we are attempting to access via local sign on.
We believe we have set the local user flag in both our normal account and the test account per the documentation; but are encountering an Nginx 403 error page when attempting to sign-in via https://{domain-name}/ECM/login/authsaviynt .
We are setting the localauthenabled flag via the Update User GUI on the Home page, is this not the correct place that this flag is configured? Is this a known issue and what are potential remedies?
12/08/2022 12:24 PM - edited 12/08/2022 12:25 PM
Saviynt must have blocked url to use for internal team,
Raise saviynt FD ticket to confirm same.
similar post https://forums.saviynt.com/t5/identity-governance/authsaviynt-url-is-unaccessible/m-p/18734#M8522
12/14/2022 06:20 AM
I've made a support ticket and their response was:
"Please be informed we cannot bypass access for any accounts if SSO is enabled. To access via local Sign-On, Please disable SSO and try again. When SSO is enabled all access must be via SSO only."
This seems opposite to what the documentation I'm referencing claims; has anyone else experienced this restriction? If so, what is the workflow your team uses to facilitate using test users? Making dummy SSO account credentials seems overkill.
12/14/2022 07:10 AM
Using SSO also they can login they will need Authenticator code,(if applicable)