Skip to content
Eptura
Feedback by UserVoice
← Archibus

How can we improve Archibus?

Archibus: Smart Client

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Make Smart client SAML SSO expire / re-authenticate to be more user friendly.

When user session expired in Smart client, the user will get the “Unable to connect to WebCentral server at the specified URL….” Error message and then he need to go back to the login screen to check the SAML authentication. Client found it annoying that everyday they have to close the error dialog, re-choose the project so that they can go into the login screen, then re-choose the option to pick on "USE SAML authentication" and then wait for a minute to get the login screen to load. (the whole process took about 1 - 3 minutes and so it adds up if the user use this everyday) Is there any way we can make this to be more efficient for user who is using SAML SSO?

52 votes

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

Anonymous shared this idea  ·   ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Susan Everts commented  · 

    It causes on-going user support issues because the end user has to select "Use SAML Authentication" each time they connect.

    Previously when using the Windows Authentication, the selection is set for the end user. I have a recording showing the issue that I would be happy to share with development. We would really like to see this fixed in v2024.04, this has been an issue for years.

  • Keith Simpson commented  · 

    This is an ongoing issue for users who use SAML SSO with Smart Client that affects the user adoption and experience of the application. With the significant number of up votes this has received, can this be put on the roadmap to finally be addressed?

  • Alexander Federlin commented  · 

    Working with the Smart Client using SAML SSO is absolutely painful. The constant error messages and unnecessary clicking to chose the SAML authentication that has to be done EVERY. SINGLE. TIME. you want to log in to the Smart Client is clearly a bug. Please make it stop.

  • Anonymous commented  · 

    When user session expired in Smart client, the user will get the “Unable to connect to WebCentral server at the specified URL….” Error message and then he need to go back to the login screen to check the SAML authentication. Client found it annoying that everyday they have to close the error dialog, re-choose the project so that they can go into the login screen, then re-choose the option to pick on "USE SAML authentication" and then wait for a minute to get the login screen to load. (the whole process took about 1 - 3 minutes and so it adds up if the user use this everyday) Is there any way we can make this to be more efficient for user who is using SAML SSO?