A migration to Data Center saved up to 50% of the licensing cost – but broke access to its Knowledge Base. This guide shows how to solve it.
Introduction If you’re using our SAML SSO app for Jira and you are provisioning your users with the User Sync module, you may find yourself
How cool is it to be able to log into your Data Center Jira using your Atlassian Cloud account? Or your LinkedIn profile?
How can you provision 42,000 users into a 15,000 users Jira instance without destroying usability? Learn how to set it up in this step-by-step guide.
Having a robust process for deactivating inactive users has become more important than ever. In this guide we will look at the different goals for deactivating users, typical options for hosting users, and the best alternatives for disabling them.
When moving to Data Center, you may evaluate whether the native SAML SSO is a good option. Check whether you need any of the features in this list.
API Tokens are an important piece in how Automation Consultants run their integrations with their on-premise Jira instance.
Okta’s free connectors for Jira and Confluence Server can authenticate users. But how do you solve provisioning?
- 4 Day Week (6)
- API Token Authentication (6)
- AWS ALB Authentication (1)
- Cloud (46)
- Embed apps for Confluence (16)
- Embed apps for Jira (3)
- Google Analytics (2)
- Group Management (3)
- Hubspot (5)
- Language Translation for Jira Service Management (10)
- License Management (3)
- NASA (8)
- Out of Office Assistant for Jira Cloud (13)
- Real Solutions (7)
- Real User Management Solutions (5)
- SAML SSO (20)
- User and Groups Sync (11)
- User Deactivator (5)
- User Management (34)