-
Suggestion
-
Resolution: Unresolved
-
None
-
None
Admittedly this will need the buy in of the JIRA and Confluence PM's. However, I would like to provide a guide for specific instances.
1. User or group not found.
2. Login invalid.
3. Crowd completely unavailable.
It may also help to provide guidelines for those attempting to integrate other applications with Crowd.
[CWD-1299] Provide friendlier Crowd-integrated application errors when Crowd is unavailable
Workflow | Original: JAC Suggestion Workflow [ 3388850 ] | New: JAC Suggestion Workflow 3 [ 3630878 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1389848 ] | New: JAC Suggestion Workflow [ 3388850 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: Crowd Development Workflow v2 [ 273164 ] | New: Simplified Crowd Development Workflow v2 [ 1389848 ] |
Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] |
Workflow | Original: Feature Request Workflow [ 174178 ] | New: Crowd Development Workflow v2 [ 273164 ] |
Workflow | Original: jira [ 147270 ] | New: Feature Request Workflow [ 174178 ] |
A first step on the crowd-integration client side may be to write a nicer message in the client log file when these errors occur to notify admins of the root cause.