buep
commented
9 years ago Isn't one of our goals with STACI to do the right thing for the users. Make it easy, so if we mean crowd is nice to use, offer it as an option, but either for all the STACI systems or none. Makes it simpler.
Further, why is it a problem to supply the file above? There is not reference to other containers, so when the container is build you could add the file?
This takes more efford. The application (like Jira) needs to have changes done to files in the container on build time. The file crowd.properties needs to be edited in /opt/atlassian/jira/atlassian-jira/WEB-INF/classes/. It does not exist, but it does in the Crowd container and looks like this :
atlassian@crowd:/opt/atlassian/crowd/client/conf$ cat crowd.properties application.name crowd application.password password application.login.url http://localhost:8095/crowd/console/
crowd.server.url http://localhost:8095/crowd/services/ crowd.base.url http://localhost:8095/crowd/
session.isauthenticated session.isauthenticated session.tokenkey session.tokenkey session.validationinterval 2 session.lastvalidation session.lastvalidation
But only if one choose to use Crowd.
Also, the ip of Crowd is difficult before Crowd is running. Using a DNS name would solve this. And then we've opened a hole new issue :)