Can a Custom Seraph Authenticator be shared between standalone JIRA and Confluence instances?

We already have a standalone JIRA 4.4 instance hosted internally with a custom seraph authenticator to our own enterprise Single Sign On directory. If we install a trial and eventually a licensed standalone Confluence 4.0 instance on the same physical server, can we use the same custom seraph authenticator for Confluence that we are using today for JIRA? Or do we have to maintain a different seraph authenicator for Confluence. Even if they are separate XML files, can the configurations be the same?

2 answers

1 accepted

0 votes
Accepted answer

In my opinion, a different authenticator is required because both Confluence and JIRA authenticators use their application specific libraries.

How are you implementing the custom seraph authenticator? If it is contained in a plugin, you should be able to deploy the plugin to both JIRA and Confluence. The modifications to the web.xml and seraph-config.xml should be similar to both. One thing to be aware of is that your custom seraph authenticator will need to use DefaultAuthenticator for JIRA and ConfluenceAuthenticator for Confluence. I was pointed in the right direction from an answer to one of my questions:

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Feb 06, 2019 in Confluence

Try out the new editing experience

Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...

1,337 views 96 8
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you