Ping Federate not working on Confluence
Asked by Maz Kozi:

Hi,

I am integrating JIRA and Confluence with Ping. Currently we have an easy sso setup. If I login to JIRA or Confluence, then I don't have to login again to access Confluence or JIRA. If I am in Office network, it logs me in automatically into both using my windows credentials (Kerberos setup).

After implementing ping, I see that JIRA is redirecting me to Ping for authentication, however, confluence doesn't redirect me to Ping at all. I contacted Ping and had my configs verified, all looks good. I believe something is missing from Confluence side that is not redirecting my request to Ping.   

As per the configuration guide, I have configured the authenticator in seraph-config.xml and change the login and login.link urls. I don't see the requests been handed over to this authenticator.

Can someone help me resolve this?  

Below are the details for your reference:

JIRA Version: 7.2.5

Confluence Version: 6.0.1

PingFed Version: 8.3


Answers:
author: Lokesh Naktode_miniOrange
body: It is too late to answer this question as it is 2019 and the question was from 2017 but anyone searching for SSO into JIRA and other Atlassian applications from Ping Federate or any SAML supported IDP can use the SAML SSO Plugin for [JIRA](https://marketplace.atlassian.com/apps/1215430/jira-saml-single-sign-on-sso-jira-sso?hosting=datacenter&tab=overview) and [Confluence](https://marketplace.atlassian.com/apps/1215542/single-sign-on-sso-confluence-saml?hosting=server&tab=overview).

With this plugin, you can manage the user's profile, groups, and redirection to IDP from the plugin's dashboard itself no need to change any of server file.

I work for miniOrange and in case if you need further assistance with the plugin and IDP configuration, you can reach out to miniOrange at atlassiansupport@miniorange.com or through the[customer portal](https://miniorange.atlassian.net/servicedesk/customer/portal/2).

Thanks,  
Lokesh


author: Ed Letifov _TechTime - New Zealand_
body: Well, I am late to the party (this being 2019 and the question form 2017), but for the sake of future people searching something like this...

EasySSO is a commercial plugin, fully supported 24x7...

Please reach to our Support with this kind of questions: [https://marketplace.atlassian.com/apps/1212583/easy-sso-confluence-kerberos-ntlm-saml?hosting=server\&tab=support](https://marketplace.atlassian.com/apps/1212583/easy-sso-confluence-kerberos-ntlm-saml?hosting=server&tab=support)

Having said this, based on the description of the issue, and the fact that something is being deployed in seraph-config.xml - I would imagine the issue is with something provided by Ping, i.e. their SAML authenticator, rather than EasySSO.


author: Christian Reichert (resolution)
body: Hi Maz,

like Lars above, I can't help with Easy SSO itself. I can only really point you towards our plugins in the marketplace - <https://marketplace.atlassian.com/vendors/1210947/resolution-reichert-network-solutions-gmbh>

(I work for resolution).

We have many customers to use PING via SAML with our plugins for both their external \& internal needs.

You get in touch with us at atlassianplugins@resolution.de if you like some help in setting it up.

<br />

Cheers,  
Christian


author: Lars Olav Velle
body: Disclaimer: I work for Kantega Single Sign-on.

We have a plugin that offers both Kerberos and SAML (with built-in instructions for PING)

If you want to use both in combination, then you are automaticallly logged in while at the Office, while you can use SAML remotely.

You do not have to edit any configuration files at all.

<br />

===

Perhaps a silly question, but you did restart confluence after making the changes to seraph-config.xml?

comments: author: Maz Kozi
body: Yes. I did.


Tags: sso