PAGE UNDER CONSTRUCTION
There should be a link to configure the plugin in the UI in Confluence after you install it. The plugin may need be configured appropriately before it will work properly.
- User Manager Location - use Confluence unless you are using Jira for Confluence User Management (see [Understanding User Management in Confluence] for more information)
- If you are using Jira for User/Group Managment, you will need to:
- Specify the JIRA SOAP Service Endpoint URL (for example: http://yourjiraserverhostname/rpc/soap/jirasoapservice-v2 )
- Specify a username and password (be sure to check the checkbox to the left of "Set Password" to set it) for an admin user in Jira that you want to use for user/group management.
- It will attempt to test the connection to Jira, so you'll need to make sure that the SOAP service is enabled in Jira configuration.
- If you want to use LDAP to get info for users in order to autoprovision them if they don't already exist, set "Autoprovision Users Using LDAP Info" to YES. Otherwise, set it to NO.
- If "Autoprovision Users Using LDAP Info" is set to YES, you'll need to:
- Set provider type (whether it should get LDAP info from osuser.xml or atlassian-user.xml)
- Attribute names (talk to your LDAP person to get the right values)
- Set LDAP provider fully qualified classname. This may just be "com.opensymphony.user.provider.ldap.LDAPCredentialsProvider".
- Unless you don't want space admins to create/delete groups that match the prefix/suffix specified, set Group Actions Permitted to YES.
- New Group Name Creation Pattern takes the place of the old rexexp pattern from v1.0 such that you specify a groupname prefix and/or groupname suffix for all groups to be manageable by space admins.
- Max number of user ids/group ids - this just keeps a space admin from trying to add tons of users and groups at once
- User Search Enabled - you'll want this to be YES because it really helps space admins when they only know the first/last name or email of the users they need to add (for example), unless:
- You don't want space admins seeing all users in Confluence (the only info it gives about the user is username, fullname, and email though).
- You have a ton of users (tens of thousands) and are using the old osuser schema instead of the new atlassian-user schema. (because the osuser schema is really slow for that many users)
- Personal Space User/Group Administration Allowed - choose NO if in doubt. You probably don't want users to be able to manage their own groups for personal spaces.
- Plugin Deactivated/Downtime Message - at first you may think "hey. doesn't confluence already have another mechanism to disable plugins?" However, this may be useful for some, because it allows you to specify a downtime message, which you can't currently do via normal plugin disabling.
Here are the CSUM Tasks need to perform in order to integrate Crowd with CSUM:
- Admin setting for Crowd Connector integration parameters (as needed)
- Admin setting for choosing to create groups in Jira/Confluence or via Crowd Connector
- Admin setting to set a limit on the number of groups than can be created for the space
Configuration Troubleshooting
- If you have problems with Jira integration and you are sure that it is not the connection/authentication but is an actual integration issue, it could be that the webservice definition of your Jira is incompatible with the plugin. If there is a newer version of the plugin available, please update it and see if that works. Otherwise, download a copy of the wsdl from your jira from (jiraurl)/rpc/soap/jirasoapservice-v2?wsdl and attaching that along with logs to a jira ticket for this plugin and we'll see what we can do. You can also try doing a diff of your wsdl to the jira.wsdl in plugin trunk to see what is different, and even try just checking out trunk, replacing the wsdl, and rebuilding, and deploying target/(jar name) to see if just a simple rebuild works.