-
Suggestion
-
Resolution: Low Engagement
-
None
-
1
-
The use case for having the openid-server as an external client application was so that multiple openid-servers could be run against a single Crowd server.
This fringe use-case benefit pales in comparison to the other benefits of having the openid-server built-in to the crowd-console:
- easier configuration (administration can be done via a single console)
- easier backups (1 database, not 2)
- cleaner code (no need to push things to crowd-core to make them available to openid-server)
This will require role permissioning within the Crowd application (ie. crowd-users, crowd-administrators, possibly crowd-openid-users, etc).
[CWD-766] Bring the openid-server application in to the crowd-console application
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | New: cleanup-seos-fy25 |
Support reference count | New: 1 |
Workflow | Original: JAC Suggestion Workflow [ 3389138 ] | New: JAC Suggestion Workflow 3 [ 3629568 ] |
Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392514 ] | New: JAC Suggestion Workflow [ 3389138 ] |
Issue Type | Original: Improvement [ 4 ] | New: Suggestion [ 10000 ] |
Status | Original: Open [ 1 ] | New: Gathering Interest [ 11772 ] |
Workflow | Original: Crowd Development Workflow v2 [ 271901 ] | New: Simplified Crowd Development Workflow v2 [ 1392514 ] |
Assignee | Original: David O'Flynn [Atlassian] [ doflynn ] |
Workflow | Original: Feature Request Workflow [ 173318 ] | New: Crowd Development Workflow v2 [ 271901 ] |
Workflow | Original: jira [ 121611 ] | New: Feature Request Workflow [ 173318 ] |