We have Confluence attached to Crowd and configured our User-Directory in Crowd with a default group on first login. When a user logs into Confluence for the first time, the following happens: * User gets added to the configured default group in Crowd (the group having "can use" permission) * User gets a "not permitted" error in Confluence * However, after the directory synchronisation interval of 60' the local user group in Confluence is correctly updated and the user can log in as expected How can I configure an "immediate synchronisation" between Crowd and Confluence on changes in Crowd?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

not permitted error after first login in confluence via crowd

Christian Zandee

We have Confluence attached to Crowd and configured our User-Directory in Crowd with a default group on first login.

When a user logs into Confluence for the first time, the following happens:

User gets added to the configured default group in Crowd (the group having "can use" permission)
User gets a "not permitted" error in Confluence
However, after the directory synchronisation interval of 60' the local user group in Confluence is correctly updated and the user can log in as expected

How can I configure an "immediate synchronisation" between Crowd and Confluence on changes in Crowd?

Accepted answers

Bruno Vincent

Hi Christian,

So far you can't but this issue will be resolved in Crowd 2.10 as far as I can tell from the following issue tracking: https://jira.atlassian.com/browse/CWD-2650

All comments

Steven F Behnke

Can you provide more information?

Christian Zandee

Sorry, this topic was created by mistake (instead of a support request), however, now that the question is created I'll give some more information of course:-)

Bruno Vincent

Hi Christian,

So far you can't but this issue will be resolved in Crowd 2.10 as far as I can tell from the following issue tracking: https://jira.atlassian.com/browse/CWD-2650

Christian Zandee

Thank you Bruno! As I understand from the issue, in addition to https://jira.atlassian.com/browse/CWD-2650 also https://jira.atlassian.com/browse/CONF-23957 is required which unfortunately doesn't seem to be on the Roadmap.

Steven F Behnke

I know this doesn't help much but customizing the SSO Authenticator is very approachable. It might be worth looking into.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

crowd