Astea Alliance Authentication

We use Azure for SSO and to make that work, the URL ends with

“/default_login_page.aspx?profile=Production”. 

However, once logged in, the URL changes that to end with “/default_portal.shtml”

If we copy the URL after being logged in and then use that to access Alliance, we found that this then gives you the old log in screen and you can type in the user and password as before.

We don’t want users to log in that way so we changed everyone’s password to something they don’t know, to force them to use SSO but it is handy if Support need to log in as another person.

Hi Chris,

This is a possible solution from the looks of it.  If you were still using the Astea Browser, `I believe you can remove SSO profile from Catalog - Options  (Or using the Astea Employee Portal Configuration Editor) which is effectively the same thing you are doing above in a normal web browser by adapting the URL.

I am having a chat what R&D probably Monday as I thought there was a more formal solution than doing something like this, at least in the later versions.

We’re using 15.0.4 and many users making use of the desktop application.  Would we have to use the browser to make this work.

Hi,

The suggestion from Chris was to change the URL used by the Web Employee Portal which is the browser agnostic client (e.g. MS Edge or Chrome).

It might be possible to do the same thing using the Astea Browser which is what I think you are saying when you say the desktop application though I have not tried this.

As I indicated above, please take a look at the Employee Portal’s Configuration Editor tool on the client (this is not the configuration editor on the servers) .  I incorrectly referred above also to the Catalog - Options as this does not have the default SSO Profile option for configuration.

Remove the SSO Profile value if you are not using SSO for that user:

Perhaps this will allow you users to sign in via Alliance securitywith the Astea Browser instead of your domain security SSO, at least from my understanding.

However, keep in mind that more and more functionality is moved to the Web Employee Portal and removed from normal usage in the Astea Browser with each SU release iteration. Meaning for example the service order module was migrated in SU3 and not directly available in the Astea Browser for normal users.