Troubleshooting Cloud Director Login Issues After Changing LDAP Identity Source Domain

As a VM administrator, you may encounter issues with logging into the Provider portal after changing the LDAP identity source domain at the Cloud Director level. This problem can occur when records for users are marked as stranded in tables such as org_member and usr. In this blog post, we will discuss the solution to this issue and provide SQL queries that can help you identify and remove these records.

Background Information

Cloud Director is a platform that enables organizations to manage their cloud infrastructure and resources. It provides a centralized interface for managing various cloud providers and allows users to access their resources through a single portal. When changing the LDAP identity source domain, it is essential to ensure that all user accounts are properly updated to avoid any login issues.

Symptoms of the Problem

After changing the LDAP identity source domain, users may experience difficulties logging into the Provider portal. Specifically, they may encounter errors such as:

* “Invalid credentials”

* “User not found”

* “Account disabled”

Causes of the Problem

The issue is caused by records for user accounts being marked as stranded in tables such as org_member and usr. These records are from the LDAP source and have null passwords. When trying to log in, these accounts cannot be authenticated correctly, resulting in login failures.

Solution to the Problem

To resolve this issue, you can use SQL queries to identify and remove the stranded records from tables such as org_member and usr. The following SQL queries can help you achieve this:

Query 1: Retrieves all records with is_external = 1 (LDAP source accounts)

“`sql

SELECT * FROM usr WHERE is_external = 1;

“`

Query 2: Retrieves all records with null passwords (LDAP source accounts)

“`sql

SELECT * FROM usr WHERE password = ”;

“`

Query 3: Updates the password for LDAP source accounts to a non-null value

“`sql

UPDATE usr SET password = ‘some_password’ WHERE is_external = 1;

“`

After running these queries, you should remove any records that were found to be stranded. It is essential to note that before making any changes to the DB of products, you should contact support and create an SR to get proper assistance.

Conclusion

In conclusion, this blog post has discussed a solution for logging in to Cloud Director after changing the LDAP identity source domain. By using SQL queries, you can identify and remove stranded records from tables such as org_member and usr, which will allow users to log in successfully. Remember to contact support before making any changes to the DB of products. We hope this post has been helpful, and we would appreciate any feedback or comments you may have.