Your SlideShare is downloading. ×
0
An Experts Guide toUser ManagementTips and Fixes to avoid TrapsAjay SridharSenior Support Engineer, Atlassian             ...
Agenda• User Management• Deployment Scenarios• Upgrade Tips• Troubleshooting Upgrade• Limitations                         ...
Pre JIRA 4.3 & Confluence 3.5                            Watch for details here!                                          ...
Pre JIRA 4.3 & Confluence 3.5                            Watch for details here!                                          ...
Pre JIRA 4.3 & Confluence 3.5                            Watch for details here!                                          ...
Pre JIRA 4.3 & Confluence 3.5                            Watch for details here!                                          ...
Pre JIRA 4.3 & Confluence 3.5                            Watch for details here!                                          ...
What’s new?                                             New in Confluence 3.5                                             ...
DeploymentScenarios             6
Deployment Scenario (1)                          Small Deployments:                               500 users               ...
Deployment Scenario (1)                          Small Deployments:                               500 users               ...
Deployment Scenario (2)                          Large Deployments:                          More than 500 Users          ...
Deployment Scenario (2)                          Large Deployments:                          More than 500 Users          ...
Deployment Scenario (3)                              Staging Server                                    &                  ...
Deployment Scenario (3)                              Staging Server                                    &                  ...
Upgrading            10
Upgrading• Designed to be seamless - can upgrade from any  version                                                   10
Upgrading• Designed to be seamless - can upgrade from any  version• Do not forget to copy over • atlassian-user.xml (Confl...
Upgrade Tip (1)                        Tip for:                  Large Deployments                               11
Upgrade Tip (1)                                           Tip for:                                     Large DeploymentsTr...
Upgrade Tip (1)                                           Tip for:                                     Large DeploymentsTr...
Upgrade Tip (2)                           Tip for:                  Large & Small Deployments                             ...
Upgrade Tip (2)                                                         Tip for:                                          ...
Upgrade Tip (2)                                                         Tip for:                                          ...
Upgrade Tip (3)                        Tip for:                  Large Deployments                               13
Upgrade Tip (3)                                                        Tip for:                                           ...
Upgrade Tip (3)                                                        Tip for:                                           ...
Upgrade Tip (4)                  Large & Small Deployments                        Staging Server                          ...
Upgrade Tip (4)                                             Large & Small Deployments                                     ...
Upgrade Tip (4)                                               Large & Small Deployments                                   ...
Upgrade Tip (5)                  Large Deployments                    Staging Server                               15
Upgrade Tip (5)                                      Large Deployments                                        Staging Serv...
Upgrade Tip (5)                                               Large Deployments                                           ...
Upgrade Tip (6)                          Tip for:                    Large Deployments                  Only applies when ...
Upgrade Tip (6)                                Tip for:                          Large DeploymentsTrap                    ...
Upgrade Tip (6)                                                     Tip for:                                              ...
Upgrade Tip (7)                           Tip for:                  Large & Small Deployments                   Only appli...
Upgrade Tip (7)                                  Tip for:                         Large & Small DeploymentsTrap           ...
Upgrade Tip (7)                                                       Tip for:                                            ...
Troubleshooting Upgrades                           18
Troubleshooting UpgradesIf the upgrade fails during migration                                        18
Troubleshooting UpgradesIf the upgrade fails during migration1) Check Configuration and log                               ...
Troubleshooting UpgradesIf the upgrade fails during migration1) Check Configuration and log2) Fix the problem Use Knowledg...
Troubleshooting UpgradesIf the upgrade fails during migration1) Check Configuration and log2) Fix the problem Use Knowledg...
Limitations • Duplicate users and groups • User directory ordering • Shadow users across multiple directories             ...
Why wait?• Confluence 3.5• JIRA 4.3• Fisheye/Crucible 2.6                         20
21
Questions?             21
An Expert's Guide to User Management in JIRA and Confluence
An Expert's Guide to User Management in JIRA and Confluence
An Expert's Guide to User Management in JIRA and Confluence
An Expert's Guide to User Management in JIRA and Confluence
Upcoming SlideShare
Loading in...5
×

An Expert's Guide to User Management in JIRA and Confluence

2,149

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,149
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
32
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • be more specific about the problem\n\n
  • be more specific about the problem\n\n
  • be more specific about the problem\n\n
  • be more specific about the problem\n\n
  • So the integration team at Atlassian set out to have a single library for across all products and improve the user experience for the Administrator. Requirements for the new User Management:\nOne single interface across all applications\nScalability!\nInter-operability, sharing user base using REST *\nNested Groups\nFlexible Group Membership *\nAPI for Plugin Developers\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • You will of course need to make sure that after the upgrade, you still have an admin that can log in.So - either ensure you have an admin in the local DB, or keep an LDAP config that contains an admin.It is considered good practice to have an admin account in the Internal directory (eg for if the LDAP server goes down, or changes config), so if you don't have one alreadyI would recommend you add one before you start the upgrade.\nAfter the upgrade to v4.3 or v4.3.1, you will want to add the missing LDAP connection as a "full" LDAP directory (instead of "authentication-only").That way it can do a synchronise and the system will pull all the users and groups into JIRA for you.The "LDAP authentication-only" directory (in v4.3 & v4.3.1) requires you to manually add the users to the directory - but they will already exist (in the Internal Directory), so this will be a problem.\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Here is a summary of how the directory order affects the processing:\nThe order of the directories is the order in which they will be searched for users and groups.\nChanges to users and groups will be made only in the first directory where the application has permission to make changes.\n\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Transcript of "An Expert's Guide to User Management in JIRA and Confluence"

    1. 1. An Experts Guide toUser ManagementTips and Fixes to avoid TrapsAjay SridharSenior Support Engineer, Atlassian 2
    2. 2. Agenda• User Management• Deployment Scenarios• Upgrade Tips• Troubleshooting Upgrade• Limitations 3
    3. 3. Pre JIRA 4.3 & Confluence 3.5 Watch for details here! 4
    4. 4. Pre JIRA 4.3 & Confluence 3.5 Watch for details here! 4
    5. 5. Pre JIRA 4.3 & Confluence 3.5 Watch for details here! 4
    6. 6. Pre JIRA 4.3 & Confluence 3.5 Watch for details here! 4
    7. 7. Pre JIRA 4.3 & Confluence 3.5 Watch for details here! 4
    8. 8. What’s new? New in Confluence 3.5 & JIRA 4.3• Single interface across all applications • No XML files!• Nested LDAP Groups• Built with REST from the ground up • Interoperability & Flexibility 5
    9. 9. DeploymentScenarios 6
    10. 10. Deployment Scenario (1) Small Deployments: 500 users 7
    11. 11. Deployment Scenario (1) Small Deployments: 500 users 7
    12. 12. Deployment Scenario (2) Large Deployments: More than 500 Users 8
    13. 13. Deployment Scenario (2) Large Deployments: More than 500 Users 8
    14. 14. Deployment Scenario (3) Staging Server & Mixing User Directories 9
    15. 15. Deployment Scenario (3) Staging Server & Mixing User Directories 9
    16. 16. Upgrading 10
    17. 17. Upgrading• Designed to be seamless - can upgrade from any version 10
    18. 18. Upgrading• Designed to be seamless - can upgrade from any version• Do not forget to copy over • atlassian-user.xml (Confluence) • osuser.xml (JIRA) • crowd.properties (Crowd) 10
    19. 19. Upgrade Tip (1) Tip for: Large Deployments 11
    20. 20. Upgrade Tip (1) Tip for: Large DeploymentsTrapSynchronizing large LDAP user base 11
    21. 21. Upgrade Tip (1) Tip for: Large DeploymentsTrapSynchronizing large LDAP user baseTrick• Apply more focused search filter• Split into multiple directories• Set userSearchAllDepths to false 11
    22. 22. Upgrade Tip (2) Tip for: Large & Small Deployments 12
    23. 23. Upgrade Tip (2) Tip for: Large & Small DeploymentsTrap• Upgrade fails due to Mis-configured LDAP definition 12
    24. 24. Upgrade Tip (2) Tip for: Large & Small DeploymentsTrap• Upgrade fails due to Mis-configured LDAP definitionTrick• Check LDAP configuration • Incorrect BaseDN - not containing OU • Using Paged results (LDAP Error code 4) 12
    25. 25. Upgrade Tip (3) Tip for: Large Deployments 13
    26. 26. Upgrade Tip (3) Tip for: Large DeploymentsTrapLost LDAP/local group memberships in Confluence afterupgrade • Forgot to copy over atlassian-user.xml file 13
    27. 27. Upgrade Tip (3) Tip for: Large DeploymentsTrapLost LDAP/local group memberships in Confluence afterupgrade • Forgot to copy over atlassian-user.xml fileTrick • Run the user migration manually from 13
    28. 28. Upgrade Tip (4) Large & Small Deployments Staging Server 14
    29. 29. Upgrade Tip (4) Large & Small Deployments Staging ServerTrap• Upgrade Task failure when migrating LDAP configuration 14
    30. 30. Upgrade Tip (4) Large & Small Deployments Staging ServerTrap• Upgrade Task failure when migrating LDAP configurationTrick• Remove LDAP configuration before upgrading 14
    31. 31. Upgrade Tip (5) Large Deployments Staging Server 15
    32. 32. Upgrade Tip (5) Large Deployments Staging ServerTrap• Multiple LDAP definitions in JIRA 15
    33. 33. Upgrade Tip (5) Large Deployments Staging ServerTrap• Multiple LDAP definitions in JIRATrick• Remove LDAP configuration before upgrading 15
    34. 34. Upgrade Tip (6) Tip for: Large Deployments Only applies when using OsUser & Confluence 16
    35. 35. Upgrade Tip (6) Tip for: Large DeploymentsTrap Only applies when using OsUser & ConfluenceConfluence and OsUser 16
    36. 36. Upgrade Tip (6) Tip for: Large DeploymentsTrap Only applies when using OsUser & ConfluenceConfluence and OsUserTrickMigrate to atlassian-user before upgrading 16
    37. 37. Upgrade Tip (7) Tip for: Large & Small Deployments Only applies when using OsUser & Confluence 17
    38. 38. Upgrade Tip (7) Tip for: Large & Small DeploymentsTrap Only applies when using OsUser & ConfluenceUsing JIRA’s user base 17
    39. 39. Upgrade Tip (7) Tip for: Large & Small DeploymentsTrap Only applies when using OsUser & ConfluenceUsing JIRA’s user baseTrickRemove JIRA configuration, re-add after upgrading 17
    40. 40. Troubleshooting Upgrades 18
    41. 41. Troubleshooting UpgradesIf the upgrade fails during migration 18
    42. 42. Troubleshooting UpgradesIf the upgrade fails during migration1) Check Configuration and log 18
    43. 43. Troubleshooting UpgradesIf the upgrade fails during migration1) Check Configuration and log2) Fix the problem Use Knowledge Base, jira.a.c and confluence.a.c Contact Support 18
    44. 44. Troubleshooting UpgradesIf the upgrade fails during migration1) Check Configuration and log2) Fix the problem Use Knowledge Base, jira.a.c and confluence.a.c Contact Support3) Start from the beginning 18
    45. 45. Limitations • Duplicate users and groups • User directory ordering • Shadow users across multiple directories 19
    46. 46. Why wait?• Confluence 3.5• JIRA 4.3• Fisheye/Crucible 2.6 20
    47. 47. 21
    48. 48. Questions? 21
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×