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
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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