On our production JIRA server (5.2), when I create a new group in Jira, it ends up being read-only by default and does not propagate itself into Crowd. This does not happen on our dev server, where the group is automatically write-enabled and pops up into Crowd immediatly. Where is that behavior set?
I checked the said permissions and they're the same on both sides. Actually, I see 8 permission checkboxes in Crowd 2.6.0 instead of the 2 documented here, and no Read-only option.
Hi Luc, The settings are available in JIRA, where you configure the Crowd directory. Regards, Geert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Modifying the Crowd directory in Jira requires a "local user" (i.e. defined in the JIRA Internal Directory as opposed to Crowd) but while creating such a user works, its login always fails. Can Jira's login work without Crowd?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It cannot if you enabled SSO. One option is to create a new directory with the same settings, move that one "up" and then disable/remove the old one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Maybe these settings are different between dev and production?
Regards,
Geert
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.