-
Suggestion
-
Resolution: Low Engagement
-
None
-
4
-
Currently, there are two files which need to be edited for tweaking the Crowd client library: crowd.properties and crowd-ehcache.xml.
It would be good if there was a single file which users can edit to configure the Crowd client. This could be achieved by rolling in the cache configuration in to the crowd.properties file or by creating a single XML configuration.
Currently, users are unable to tweak the transport layer configuration, such as:
- Max size of connection pool
- GZip requests
- etc, see http://xfire.codehaus.org/HTTP+Transport for other possible parameters.
They should be configurable via the new properties/XML file.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CWD-609] Single point for Crowd client configuration
Sub task has been created to speed up development to allow for configuration of HTTP proxy and connection pooling via crowd.properties.
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