Atlassian Access SAML with NetIQ

[Eric Wong]

My organization is planning to get Atlassian Access, and we were exploring to integrate using SAML with our existing Identity Manager from Microfocus NetIQ.

1. In the documentation https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html -- NetIQ was not listed as an identity provider.

2. To configure in NetIQ i would require Metadata of Atlassian 

Question:

1. Would Atlassian Access in work with NetIQ?

2. Where can i acquired the necessary Metadata and x509 cert from atlassian?

[João Nunes · Accepted solution]

Hi, Eric!

We hope you are doing well. 

To provide you with more details, before you can start configuring SAML at our end, you will need to complete the following tasks:

1. Have an Organization 
2. Verify a domain and claim the accounts
3. Subscribe to Atlassian Access

Now, Addressing your questions:

1. Would Atlassian Access in work with NetIQ?

If your Identity Provider (NetIQ) supports SAML 2.0 protocol, you should be able to configure that integration between NetIQ and Atlassian. NetIQ is not listed in our SAML Doc because they don't have a public documentation about how to set up that integration, therefore, you may need to double-check with their support team how that can be configured at their end.

2. Where can i acquired the necessary Metadata and x509 cert from atlassian?

The cert should come from your NetIQ, if I'm not mistaken. 

Bonus track: To configure in NetIQ i would require Metadata of Atlassian 

Atlassian metadata (SP Entity ID and the Assertion Consumer Service URL) is only generated after you enter the Identity Provider Entity ID, SSO URL, and the cert (at https://admin.atlassian.com > select your Org > Security > SAML Single Sign-on - note that you will only see the option to configure it after you do the tasks mentioned above).

I hope this clarifies your questions. In case you have any additional one, we will be happy to help :)

João Nunes

Atlassian Support Team

[Eric Wong]

Thanks João Nunes, i managed to resolve it through trial and error. cheers

[Viktu Pons Colomer]

@Eric Wong I am in the same boat. Can you please give me a hint on how to configure that?

Thank you!

[Michel Aguilar]

@Eric Wong This will also help us. We are also looking to use NetIQ.

[Viktu Pons Colomer]

Hi @Michel Aguilar , I got it to work.

The working config is:

SOAP Back Channel Security Method -> Message Signing

Name Identifier Format: Only "Email" -> Here add an atribute including user's email

Use proxied requests -> True

x509 certificate is the https certificate of https://auth.atlassian.com

If you have any questions let me know!

[Michel Aguilar]

Great. Thanks

So indeed I need to pay for Atlassian Access (license-add-in). right?

In my case, Atlassian Access comes with a high cost on top of the current subscription. =(

[Viktu Pons Colomer]

Yes, you need Atlassian Access licenses.

Atlassian move to the cloud is a x2 or x3 multiplier by price. They are abusing of its market position.

We are very deceived of the movement, we are forced to move to the cloud and our policy is to have everything on-premise.

I just hope that some day a good competitor appears, to get rid of a company that treats its clients that bad.

[Michel Aguilar]

And nothing has changed since then.

[Michel Aguilar]

Hi @João Nunes this means its a must to have Atlassian Access Microfocus NetIQ.