For testing purposes, it would be convenient if only the origin application needed to be taken down for configuration, while the destination remained online, unmodified.
files to be edited are for example:
the crowd.properties must be editied to fit your installation (crowd URL, application name&passwd)
in the seraph-config.xml you will need to comment out the internal authenticator and comment in the crowd authenticator.
like this: (this is for confluence)
<!-- Default Confluence authenticator, which uses the configured user management for authentication. --> <!--<authenticator class="com.atlassian.confluence.user.ConfluenceAuthenticator"/>--> <!-- Authenticator with support for Crowd single-sign on (SSO). --> <authenticator class="com.atlassian.confluence.user.ConfluenceCrowdSSOAuthenticator"/>
of course you need to restart confluence afterwards
Hello Community, Today we are going to talk about the three Scrum Roles. There is the Development Team, the Scrum Master and the Product Owner. In my opinion these three are all really impo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs