• State Not Answered
  • Replies replies
    10
  • Subscribers subscribers
    17
  • Views views
    808
  • Users 0 members are here

Poor performance when login on Windows client

Jens Schmitz

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 Reply Children
  • 0 in reply to   

    There have been no updates, only information indicating that the ticket is in development. We've been waiting for months without any results. Logon processes are taking excessively long, as evident from the logs....

    Additionally, there appears to be an issue with Nginx. However, we're unable to modify any settings within the Nginx container. We're hesitant to open a new ticket because there has been no progress made on the existing one....:

    2024-03-19 15:35:55 (UTC+0100) [warn] 32#32: *60742 an upstream response is buffered to a temporary file /usr/local/nginx/uwsgi_temp/7/47/0000000477 while reading upstream



Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.