If it helps, I can re-test on our instance with logoutEndpoint left empty (so discovery is used) and post the full redirect chain from the logs.
My main concern is what to do with this issue exactly
From what I understand, what would make the most sense would be to change the title to something like "Logout mechanism appear in the configuration object" and just cleanup all that.
AFAIK OIDC logout in general works fine. If it turns out that you have a problem specific to EntraID with it (but I know quite a few users do use EntraID already so I would expect something like this to be reported already), the cleanest would probably be to create a new dedicated issue as this one is starting to be pretty messy and hard to follow.
Thomas Mortagne on 29/Sep/26 16:02
bq. If it helps, I can re-test on our instance with logoutEndpoint left empty (so discovery is used) and post the full redirect chain from the logs.
My main concern is what to do with this issue exactly :)
From what I understand, what would make the most sense would be to change the title to something like "Missleading 'Logout mechanism' appear in the configuration object" and just cleanup all that.
AFAIK OIDC logout in general works fine. If it turns out that you have a problem specific to EntraID with it (but I know quite a few users do use EntraID already so I would expect something like this to be reported already), the cleanest would probably be to create a new dedicated issue as this one is starting to be pretty messy and hard to follow.
Thomas Mortagne on 29/Sep/26 16:02
bq. If it helps, I can re-test on our instance with logoutEndpoint left empty (so discovery is used) and post the full redirect chain from the logs.
My main concern is what to do with this issue exactly :)
From what I understand, what would make the most sense would be to change the title to something like "Missleading 'Logout mechanism' appear in the configuration object" and just cleanup all that (if someone do want to implement that one day, it can be put back).
AFAIK OIDC logout in general works fine. If it turns out that you have a problem specific to EntraID with it (but I know quite a few users do use EntraID already so I would expect something like this to be reported already), the cleanest would probably be to create a new dedicated issue as this one is starting to be pretty messy and hard to follow.
This message was sent by Atlassian Jira (v9.3.0#930000-sha1:287aeb6)
If image attachments aren't displayed, see this article.
