-
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).
Hello,
Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.
Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.
Please note the comments on this thread are not being monitored.
You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.
To learn more about our recent investments in Crowd Data Center, please check our public roadmap.
Kind regards,
Crowd Data Center