Poor performance when login on Windows client

Hey all,

does anyone else also has a poor performance when login on a Windows client?

After entering the Windows username, the AA Windows client loads the user's available chains. This process takes between 4 and 12 seconds. After this delay, users can select the chain and proceed. However, each step within the chain also has a delay, so it can be said that the login is significantly longer than without aa service (10-30 sec). This is not really acceptable and does not improve the acceptance of the tool...


In Webserver Logs i can see the delay too:

2024-02-23 15:32:53 (UTC+0100) INFO [uwsgi-end-req] GET /api/v1/custom_messages?category=messages&encrypt_secrets=true&endpoint_session_id=**ID** **NLB-IP** 81ms
2024-02-23 15:32:53 (UTC+0100) INFO [uwsgi-end-req] GET /api/v1/repositories?encrypt_secrets=true&endpoint_session_id=**ID** **NLB-IP** 14ms
2024-02-23 15:32:53 (UTC+0100) INFO [uwsgi-end-req] GET /api/v1/endpoints/**ID**/effective_policy?endpoint_session_id=**ID** **NLB-IP** 112ms
2024-02-23 15:32:56 (UTC+0100) INFO [uwsgi-end-req] GET /smartphone **NLB-IP** 1ms
2024-02-23 15:32:57 (UTC+0100) INFO [aucore.au.ldap.ldap_repo] Cached group was found
2024-02-23 15:32:58 (UTC+0100) INFO [aucore.au.ldap.ldap_repo] Cached group was found
2024-02-23 15:32:59 (UTC+0100) INFO [aucore.au.ldap.ldap_repo] Cached group was found
2024-02-23 15:33:01 (UTC+0100) INFO [aucore.au.ldap.ldap_repo] Cached group was found
2024-02-23 15:33:01 (UTC+0100) INFO [aucore.au.ldap.ldap_repo] Cached group was found
2024-02-23 15:33:01 (UTC+0100) INFO [aucore.au.ldap.ldap_repo] Cached group was found
2024-02-23 15:32:53 (UTC+0100) INFO [uwsgi-end-req] GET
2024-02-23 15:32:53 (UTC+0100) INFO [uwsgi-end-req] GET /api/v1/logon/chains?encrypt_secrets=true&endpoint_session_id=**ID**&event=Windows%20logon&include_all_chains=true&user_name=**DomainAndUser** **NLB-IP** 7542ms

Does anyone else have this problem?

Kind regards.

Jens

Parents
  • 0  

    Hello Jens,

    We have an open ticket for you about this with Development. I just reached out to Development again to see if they can provide any feedback.

    It would be interesting to see if any other customer here can share if they have the same issue.

    I'll keep you informed.

    Thanks.

    Regards,

    Luciano Testa

  • 0 in reply to   

    Hey Luciano Testa,

    Yes, I know. Our ticket has been open since September 18, 2023, and a second ticket since Friday (February 23, 2024). But I'd like to check if anyone from the community is experiencing the same issues and might have a solution. We're severely restricted in our usage.

    Regards,
    Jens

Reply
  • 0 in reply to   

    Hey Luciano Testa,

    Yes, I know. Our ticket has been open since September 18, 2023, and a second ticket since Friday (February 23, 2024). But I'd like to check if anyone from the community is experiencing the same issues and might have a solution. We're severely restricted in our usage.

    Regards,
    Jens

Children