but returns an error on valid accounts (email address)
Are you still getting this error? If so, can you have a look at Indicium’s error log and see if it contains more details regarding this error? If the details seem sensitive in nature, then I would recommend creating a ticket instead.
Well. This messed things up a bit. I have made the changes to the appsettings and IAM as described, but it didn't work and the signon screen is now messed up.
It seems like you have either configured an OpenID provider or Two-factor authentication in IAM, in both of these cases the Universal GUI can no longer handle the authentication itself and it will delegate this to Indicium. It is possible that email 2FA had already been configured on your user and that configuring an email provider in IAM caused it to enable.
The Forget Email passwords are sent out by Indicium and do require configuration to my knowledge. Depending on your platform version, you may need to alter the appsettings.json of Indicium or setup the correct values in IAM for the System email provider.
Well. This messed things up a bit. I have made the changes to the appsettings and IAM as described, but it didn't work and the signon screen is now messed up. I tried a different computer and browser, but the sign-on problem persists:
I can move past it and click two additional times to get to the sign-on screen. The original problem also stil exists.
What I would like to have is a clear step by step document for this. This is taking more time than it should. Most steps I need to perform are quite simple though need some time to execute. However it is easy to make a single mistake or take a wrong turn which makes things not work.
but returns an error on valid accounts (email address)
Are you still getting this error? If so, can you have a look at Indicium’s error log and see if it contains more details regarding this error? If the details seem sensitive in nature, then I would recommend creating a ticket instead.
Well. This messed things up a bit. I have made the changes to the appsettings and IAM as described, but it didn't work and the signon screen is now messed up.
It seems like you have either configured an OpenID provider or Two-factor authentication in IAM, in both of these cases the Universal GUI can no longer handle the authentication itself and it will delegate this to Indicium. It is possible that email 2FA had already been configured on your user and that configuring an email provider in IAM caused it to enable.
The Forget Email passwords are sent out by Indicium and do require configuration to my knowledge. Depending on your platform version, you may need to alter the appsettings.json of Indicium or setup the correct values in IAM for the System email provider.
Well. This messed things up a bit. I have made the changes to the appsettings and IAM as described, but it didn't work and the signon screen is now messed up. I tried a different computer and browser, but the sign-on problem persists:
I can move past it and click two additional times to get to the sign-on screen. The original problem also stil exists.
What I would like to have is a clear step by step document for this. This is taking more time than it should. Most steps I need to perform are quite simple though need some time to execute. However it is easy to make a single mistake or take a wrong turn which makes things not work.
but returns an error on valid accounts (email address)
Are you still getting this error? If so, can you have a look at Indicium’s error log and see if it contains more details regarding this error? If the details seem sensitive in nature, then I would recommend creating a ticket instead.
Well. This messed things up a bit. I have made the changes to the appsettings and IAM as described, but it didn't work and the signon screen is now messed up.
It seems like you have either configured an OpenID provider or Two-factor authentication in IAM, in both of these cases the Universal GUI can no longer handle the authentication itself and it will delegate this to Indicium. It is possible that email 2FA had already been configured on your user and that configuring an email provider in IAM caused it to enable.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.