Troubleshooting User Management
Stash Knowledge Base Home
- Stash Technical Alerts
- Troubleshooting Git
- Troubleshooting Installation
- Troubleshooting JIRA Integration
- Troubleshooting Performance
- Troubleshooting Project Management
- Troubleshooting User Management
- Miscellaneous
- Troubleshooting Databases
- 'How Do I...' and 'How to...' Guide to Stash
- Troubleshooting Repositories
- Troubleshooting Backup Client
- Troubleshooting Stash Data Center
- JAVA Option '-Dhttp.nonProxyHosts' Does Not Work on Windows OS
- Cannot delete a Stash repository due to 'HT_sta_pr_activity does not exist' error
On this page
In this section
- <User> cannot be deleted; they belong to a read-only directory.
- Cannot Login to Stash Using External User Account After Moving JIRA/Crowd Server
- Configure Gravatar URLs in Stash
- Could not retrieve SSO Configuration when integrating Stash with Crowd
- Creating new users fails when Delegated LDAP is configured with Stash
- Crowd Synchronization Fails with Integrity Constraint Violation
- Directory server synchronization failed
- LDAP Error Code 32
- LDAP Error Code 49
- SizeLimitExceededException when integrated with LDAP
- SSLHandshakeException - unable to find valid certification path to requested target
- Stash displays 404 j_stash_security_check after User Directory modifications
- Stash throws 500 error when attempting to edit an External User Directory
- Synchronization with LDAP Server Fails with PartialResultException
- Unable to Add Crowd User to Local Stash Group
- Unable to add Global permissions to groups
- Unable to connect to JIRA for authentication - Forbidden 403
- Unable to find the username of the principal
- Unable to login into Stash after turning on Crowd integration
- Unable to sync crowd user directory - query did not return a unique result
- Users can't access Stash due to Google Apps For Crowd plugin in Crowd
Related content
- No related content found
Last modified on Apr 24, 2012
In this section
- <User> cannot be deleted; they belong to a read-only directory.
- Cannot Login to Stash Using External User Account After Moving JIRA/Crowd Server
- Configure Gravatar URLs in Stash
- Could not retrieve SSO Configuration when integrating Stash with Crowd
- Creating new users fails when Delegated LDAP is configured with Stash
- Crowd Synchronization Fails with Integrity Constraint Violation
- Directory server synchronization failed
- LDAP Error Code 32
- LDAP Error Code 49
- SizeLimitExceededException when integrated with LDAP
- SSLHandshakeException - unable to find valid certification path to requested target
- Stash displays 404 j_stash_security_check after User Directory modifications
- Stash throws 500 error when attempting to edit an External User Directory
- Synchronization with LDAP Server Fails with PartialResultException
- Unable to Add Crowd User to Local Stash Group
- Unable to add Global permissions to groups
- Unable to connect to JIRA for authentication - Forbidden 403
- Unable to find the username of the principal
- Unable to login into Stash after turning on Crowd integration
- Unable to sync crowd user directory - query did not return a unique result
- Users can't access Stash due to Google Apps For Crowd plugin in Crowd
Related content
- No related content found
Powered by Confluence and Scroll Viewport.