Skip to main content

How do I resolve login and logout issues with the Umbraco Cloud backoffice?

Joana Knobbe avatar
Written by Joana Knobbe
Updated over 3 weeks ago

Resolving Login and Logout Issues with the Umbraco Cloud Backoffice

Encountering login or logout issues when trying to access the Umbraco Cloud backoffice can be frustrating. This guide provides a step-by-step resolution for two common problems: users being logged out immediately after logging in, and being stuck on the /umbraco-signin-oidc URL after login.

Common Causes of Backoffice Login and Logout Issues

These access issues typically occur due to one of the following:

  • Permissions Misalignment: Users are not properly added to both the Umbraco Cloud Portal and the CMS backoffice.

  • Misconfigured Data Types: After upgrading Umbraco CMS, specific configurations (e.g., Multi-Node Tree Picker) may contain invalid values that prevent the backoffice from loading.

Step-by-Step Solutions

1. Fixing Immediate Logout After Login

If users are being logged out of the backoffice right after logging in:

  1. Verify User Addition to Umbraco Cloud Portal: - Ensure the user is added to the Umbraco Cloud Portal. - Note: Users can be added to the Portal without being granted access to specific environments if necessary.

  2. Update Backoffice Permissions: - Assign the correct permissions to the user in the CMS backoffice.

  3. Align Portal Membership and Backoffice Permissions: - Once the user’s permissions are properly configured across both the Cloud Portal and backoffice, this issue should resolve.

2. Fixing Redirect Issues After Upgrade

If you are stuck on /umbraco-signin-oidc and not redirected to the backoffice, this could be due to an invalid data type configuration:

  1. Check Error Logs: - Look for errors related to data type configurations (e.g., Multi-Node Tree Picker) in the trace logs. Specifically, check for issues pointing to invalid GUIDs.

  2. Identify the Problematic Data Type: - Use the ID mentioned in the error logs to locate the data type causing the issue.

  3. Correct Configuration Values: - Open the relevant data type (e.g., Multi-Node Tree Picker) in the backoffice. - Ensure that all GUID fields, like startNode.id, are valid and correspond to existing nodes. - If needed, reselect the appropriate start node(s) so that the configuration serializes valid GUIDs.

  4. Save Changes and Restart the App: - Save the corrected data type configuration. - Recycle the app or restart the site to apply the changes.

  5. Retry Login: - Log back into /umbraco to confirm the issue is resolved.

Note: This issue is more likely to arise after upgrading the CMS to a new version, where stricter parsing of configurations may expose previously unnoticed errors.

Preventative Measures

To avoid future access issues:

  • Regularly review and update user permissions in both the backoffice and Umbraco Cloud Portal.

  • Validate data type configurations after CMS upgrades to ensure no invalid legacy values persist.

By following these solutions and best practices, you should be able to troubleshoot and resolve most login or logout issues with your Umbraco Cloud backoffice.

Did this answer your question?