Share via

AD Sync issues

Anonymous
2024-09-06T03:13:05+00:00

Hi Team,

Good day.

I would like to check.

We were having an issue whereby a particular application users mentioned that they were not able to login to an application which is AD synched for single sign on. But after a while they were able to connect.

When checked from AD perspective, it looks normal with sync.

Could you please advise on what could be an issue that can be happening resulting in users having intermittent login issues.

Regards,

PA

Windows for business | Windows Server | Directory services | Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

Answer accepted by question author

Anonymous
2024-09-06T07:02:12+00:00

Hi Phaandiyan Anparasan,

Thank you for posting in the Microsoft Community Forums.

Network Problems:

DNS resolution issues: check that the DNS server is stable and resolves application URLs correctly.

Network delays or interruptions: Network fluctuations may cause connections to come and go. Network monitoring tools can be used to check the stability and latency of the network connection.

Firewall or security group settings: Make sure there are no firewall rules or security group policies preventing users from accessing the application.

Authentication service issues:

Authentication server load: If the authentication server responds slowly or times out under high load, it may cause login failure. Check the server's performance metrics, such as CPU utilization, memory usage, and response time.

Failed authentication services: Although you mentioned that AD synchronization is working fine, there may be problems with authentication services (such as ADFS, SAML IDP, etc.). Check the logs of these services for errors or warnings.

Single Sign-On (SSO) Configuration:

SSO misconfiguration: check that the SSO configuration between the application and AD is correct. Include any necessary certificate, key, URL, and protocol settings.

Token expiration: If the SSO mechanism relies on tokens (e.g., OAuth, SAML tokens), make sure that the expiration date of the token is set appropriately and that there are no login failures due to expired tokens.

Client-side issues:

Browser cache or cookie issues: clearing browser cache and cookies may resolve some intermittent login issues.

Client time out of sync: If the time of the client device differs significantly from the server time, security features such as SSL certificate validation may be affected.

AD synchronization delays:

Although you mentioned that the synchronization appears to be normal, occasional delays or synchronization errors can cause problems. Check the AD synchronization logs to make sure there are no delays or errors.

Password Synchronization Issues: if password synchronization is part of SSO, ensure that the password synchronization service is running properly and that there are no delays.

Log Analysis:

Check application logs: check the application log files for detailed error messages about failed logins.

View AD and authentication service logs: these logs may contain more detailed information about authentication failures.

User account issues:

Account lockout: check to see if any user accounts are locked out due to multiple failed login attempts.

Account Permissions: Ensure that the user account has the appropriate permissions required to access the application.

Best regards

Neuvi

Was this answer helpful?

0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2024-09-19T02:49:27+00:00

    Hi Neuvi,

    Thanks. It was due to an network POC done at a site that caused the delay for the replication.

    It has now been fixed.

    Thanks.

    PA

    Was this answer helpful?

    0 comments No comments