/
SSO for NUS accounts using Atlassian services

SSO for NUS accounts using Atlassian services

Owned by KP
Last updated: 31 Jan 2025
4 min read

Implementation of SSO for NUS accounts for Atlassian services

We intend to implement SSO (single sign-on) for Atlassian services for NUS users after Friday, 7 February 2025. The date is subject to confirmation, but it will not be earlier than this date.

If you use Atlassian services with your NUS Friendly Mail alias, you need to create an Atlassian account using your NUS-ID email or with an alternative, non-NUS email address.

If you are an alumni who uses your lifelong NUS email for your Atlassian account, you will need to create an Atlassian account with a non-NUS email address.

Once you create the new Atlassian account:

  1. If you do not manage the service that you use, you will need to ask the respective service administrator to add you to the service using this new Atlassian account. e.g. If you have access to a Confluence wiki, the admin will have to add this new account to the wiki.

  2. If you are the product admin of the service that you use, you need to add the new Atlassian account to the service, then provide administration rights to the new account. You may also want to remove the old account from the service.

  3. If you subscribe to the Atlassian service, you should also add the new Atlassian account as a billing admin.

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

Frequently Asked Questions (FAQs)

Background

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. The earliest it will be implemented is on the weekend of Saturday 8 February. If you are currently using your NUS friendly-mail for your Atlassian account, please take the necessary action as soon as possible.

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.

Creating a new Atlassian account

Can I change the email address of my Atlassian account from friendly-mail to NUS-ID email instead of creating a new Atlassian account?

As a preparatory step to implementing SSO, NUS has had to claim all nus.edu.sg and u.nus.edu email addresses. As such, they are considered managed accounts. The email addresses are thus fixed and cannot be changed by the users nor the organisation administrators.

I am an NUS alumni with an Atlassian account under my lifelong email address. What should I do?

You should create an Atlassian account using a non-NUS email address, and make sure you can access (and manage, if applicable) the Atlassian service(s) which you use using the new account. NUS alumni will not be able to log in via SSO to Atlassian services once SSO is implemented.

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. If you are using Atlassian services that do not involve NUS, you may consider setting up a new Atlassian account with a non-NUS email address and adding the new account to the service(s) that you use/manage.

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 create a new Atlassian account with your actual NUS-ID email address so that you do not have issues moving forward.

If I do not create new Atlassian account with my NUS-ID email address and are not added back to the services I belong to or manage by the time SSO is implemented, what will happen?

You will lose access to the services you use or manage with the Atlassian account registered to your friendly-mail alias.

I do not use Atlassian services for NUS-related matters. Can I register a new Atlassian account using a non-NUS email instead?

Yes, you create an Atlassian account using a non-NUS email address. In fact, this is preferred. Please make sure that you have access to the services you use/manage using the non-NUS Atlassian account.

Others

I have other questions, who can I contact?

NUS users can use the the CTLT Helpdesk.

Alumni who were contacted can reply to the email announcement about SSO for Atlassian services.

For Atlassian service-specific support, please contact Atlassian Support.