Gonchik Tsymzhitov Community Champion

That has been shipped :) and it's easy https://big.ideas.aha.io/ideas/APP-I-4467 Sorry for the delay

Please, checkout https://confluence.atlassian.com/crowd/crowd-sso-2-0-967322291.html

Hi! You can exclude from sso scope using local directory. OR you can do cookie authentication.

Hi! Unfortunately, I have not met with use case in my company. hence I did aggregator in ADFS side

Hi! GPID will help you as identifier. And about converting name I do mostly via sql. Or time to time I do on AD level changes via other properties

It will be interesting to know how did you fix it.

In DC, solution we did via revers proxy wrapper

 Please, look into seraph. At the moment a lot of app in marketplace to that activity. Also, Atlassian provide a SAML for DC and cloud solutions

+1 I will be happy if someone provided. At the moment I did via kantego, but the first pre-auth does not work in outlook app 2016 and BlackBerry Work with last security patches

Please, checkout https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_enable-console-saml.html https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_providers_saml_3rd-party.html

Here written that option :) https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html

How about wrap via kerberos tickers

Please, checkout that KB https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html

I would say yes, because DC is using SAML

Hi! Please, next time share a logs. but at the moment is using the DC solution with SAML is good.

Hi! I think it was problem with group membership and permissions

Please, checkout the next KB: * https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html * https://confluence.atlassian.com/adminjiraserver/saml-sso-for-jira-data-center-applications-938847031.html

I think it's too late to answer. and it has been fixed as Atlassian introduced one place to auth

Do you mean merge 2 accounts?

you need to introduce a secure integration based on your log The application base URL is not HTTPS

You can use package kerberos or double check exist implementation https://github.com/atlassian-api/atlassian-python-api/pull/692 or another option use cookie-authentication

You can set exclusion url, user agents or ip addresses

Hi! it's so complicated. Maybe better to do in next way: 1. Crowd is central which connected via SAML to G-Suite 2. Other apps connected to app. Or if you have time: 1. Without Crowd connect each instance to G-Suite

Hi! You can reuse lower level httpclient as it's parent of rest client https://www.baeldung.com/java-apache-httpclient-cookies

Please, checkout https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html

If we speak about that group of app, https://marketplace.atlassian.com/apps/1217565/global-sso-single-signon-for-jira-saml?hosting=server&tab=support maybe better to raise direct request. 

Hi! Have you tried to clean config and do it from scratch? 

Hi @felix.weber , Did you find a solution? If so, please, share :) 

Hi! You can checkout using the some app, like Kantego. or Confluence DC provide the SAML support which will help you. 

Hi! Both are support SAML * https://slack.com/intl/en-ru/help/articles/203772216-SAML-single-sign-on * https://confluence.atlassian.com/cloud/saml-single-sign-on-943953302.html Hence you can integrate with okta, adfs. g-suite etc