Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 4 Next »

Implementation of SSO for NUS accounts for Atlassian services

We will be implementing SSO (single sign-on) for Atlassian services for NUS users soon.

If you use Atlassian services with your NUS Friendly Mail alias, you need to change the email of your Atlassian account to your actual NUS-ID email.

Atlassian services include (common ones in bold):

  • Atlas

  • Bamboo

  • Bitbucket

  • Compass

  • Confluence

  • Crowd

  • Crucible

  • Fisheye

  • Guard

  • Jira (and all JIRA-based products)

  • Loom

  • Sourcetree

  • Statuspage

  • Opsgenie

  • Rovo

  • Trello

Steps to change the email address of your Atlassian account

  1. Go to https://home.atlassian.com/.

  2. You will be prompted to log in, if you are not already logged in.

  3. Enter your email address.

  4. Click Continue.

    Enter email address, click Continue.
  5. Click your user profile image on the top right.

  6. Click Account settings.

    Click user profile image, click Account settings.
  7. Click the Email tab.

  8. You will see the field for New email address. Enter your NUS-ID (actual) email address.

  9. Click Save changes.

    Enter new email address, then Save.
  10. You will see a message: Update pending verification. Look out for the verification email in your NUS email inbox.
    Do also check your spam folder, the spam folder of the third-party email that you forward your NUS email to (if you do this) and the NoSpamMail daily summary (if you are NUS staff) if you have not received the verification email.

    10-verify-email.png
  11. In the email, click Verify your email.

    Click Verify your email.

    You will also receive another email titled Email address change request. This is to notify you that an email address change has been requested, no action is required for that email.

  12. Once verified, you may be asked to log in to Atlassian again. Repeat step 5 to see your new email reflected in your Atlassian account.

Frequently Asked Questions (FAQs)

Why is SSO being implemented for Atlassian services?

NUS has a subscription to an Atlassian service which requires SSO to be implemented for data and account security.

When will SSO be implemented for Atlassian services?

As of writing, the date has yet to be finalised. However, you are advised to change your Atlassian account email to your NUS-ID email as soon as possible, if you are currently using your NUS friendly-mail for your Atlassian account.

I have an Atlassian account which uses my NUS-ID email. I do not have a friendly-mail alias. What should I do?

If your Atlassian account is under your actual NUS email, you do not need to change the email of your Atlassian account i.e. no action is required.

I do not recall having an Atlassian account or I do not use my Atlassian account actively. Is any action necessary?

If you received an email notifying you that you may need to change the email address you use with Atlassian, you have an Atlassian account. However, you may not use it frequently, or you may have registered and forgotten that it exists.

While you may not need your Atlassian account now, you may need to log in to Atlassian services with your NUS email address in the future. We recommend that you proactively change your Atlassian account from your friendly-mail address to your actual NUS email address so that you do not have issues moving forward.

If I do not change my Atlassian account email address by the time SSO is implemented, what will happen?

You will not be able to log in to Atlassian services if you do not change your Atlassian account email address once SSO is implemented. You will need to contact us to resolve this.

I do not use Atlassian services for NUS-related matters. Can I change my Atlassian account to a non-NUS email instead?

Yes, you may change your Atlassian account to a non-NUS email address.

What happens to the Atlassian products that I manage or belong to?

Implementation of SSO will not change your use of nor subscription to the Atlassian products you manage or belong to. NUS will not have access to the product(s) nor take over management of the product(s). The only difference is that you will need to log in to Atlassian using SSO to access Atlassian services.

  • No labels