Thank you so much for your answer.
I created the metadata file using a web service and added:
<md:AssertionConsumerService
index="1"
Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Location="https://atlassian.start.com"; />
I'm still getting no redirection and I stay on the CAS website.
Le lundi 4 novembre 2024 à 13:38:22 UTC-5, Ray Bon a écrit :
> Neon,
>
> ACS is required in metadata.
> You can create the metadata file if the vendor does not supply it. There
> are some online services that will help.
>
> Ray
>
> On Fri, 2024-11-01 at 12:17 -0700, Neon Dazzle wrote:
>
> You don't often get email from [email protected]. Learn why this is
> important <https://aka.ms/LearnAboutSenderIdentification>
>
> Hi everyone, we have CAS6 and are trying to setup SSO with our Atlassian
> org on the cloud. It seems like we almost have it, we get redirected to CAS
> and the login works, but we can't get redirected to Atlassian after, we are
> stuck in CAS.
> It seems like there is not json parameters for redirection so I'm
> wondering where we should put the ACS adresse given by Atlassian.
> All our other services connected with CAS provide metadata files so it's
> easy, but Atlassian doesnt provide that.
> Has anyone been able to setup SSO with Atlassian Cloud?
>
>
--
- Website: https://apereo.github.io/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/a/apereo.org/d/msgid/cas-user/0f25ee5c-dfce-4ae1-b407-bee37f73047dn%40apereo.org.
