![]() Much like we stopped logging into Windows as "Administrator" and instead, elevate rights only when necessary. It's also senseless to assign super admin rights to your everyday user as then you'll never possibly face any permission issues that your co-workers might face. Before you ask, why, because IT staff comes and goes, it's senseless to assign god mode to any one person. Which is great except there's no password for since it's a _group_. Guess what: it redirects you to Azure AD login. Then you properly enroll your first user in your site, and all seems to be fine. Then you set up SAML using Azure AD, where the order in which you should do things is kinda messed up in the Atlassian portal, but you eventually figure out using the Azure docs. So you do the verification via HTTPS, whatever. So you can't verify via DNS unless you're willing to kill some of your email flow. It wants you to set (root) TXT record for verification, which I swear I've never seen anyone else do, and for a reason: that normally goes for SPF records. Then you verify your domain,, which is again more painful than should be. You enroll in Jira Service Desk + Confluence + Access trial, good. So, you register an account that will be the super administrator for your company, e.g. Actually, no, it's not all _that_ good, because you have to do this in private mode, otherwise Atlassian creates an account for you with the wrong email (your currently logged in Google account) without asking you, ever. When you create an organization in Atlassian, you are _required_ to create an Atlassian cloud account.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |