Difference between revisions of "Single sign-on"

From Charitylog Manual
Jump to: navigation, search
Line 3: Line 3:
 
1) From our website's home page, you log into your organisation, using an organisation name and password, which is shared by everyone in your organisation.
 
1) From our website's home page, you log into your organisation, using an organisation name and password, which is shared by everyone in your organisation.
  
2) This takes you to your organisation's login page within the application, where you log in with your personal user name and password. Messages from your administrator, and/or Dizions are displayed alongside the login form.
+
2) This takes you to your organisation's login page within the application, where you log in with your personal user name and password. Messages from your administrator, and/or Dizions, are displayed alongside the login form.
  
 
Long term, we are planning to replace this with a single sign-on process, which will enable you to log in using your Microsoft account, which will streamline credential management within your organisation.
 
Long term, we are planning to replace this with a single sign-on process, which will enable you to log in using your Microsoft account, which will streamline credential management within your organisation.
Line 11: Line 11:
 
1) Each organisation will have access to their own login link, which can be used instead of step 1 above. Users can bookmark this link, or if you have an intranet, it could be placed somewhere prominent.
 
1) Each organisation will have access to their own login link, which can be used instead of step 1 above. Users can bookmark this link, or if you have an intranet, it could be placed somewhere prominent.
  
2) User records will be created by default with an email address instead of a separate user name. It is already possible to use your email address as a user name, but the current login process will always refer to it as a user name. The new login process will simply ask the user for an email address, which is easier to remember.
+
2) User records will be created by default with an email address instead of a separate user name. If you use the login link, all users must use an email address instead of a user name. Users who currently have a separate user name can continue using it with the 2 step login process.
 +
 
 +
3) For organisations concerned about the removal of the need for an organisation password, we'll be making two factor authentication easier. Currently it's available using SMS messages. We'll be adding an option to use an authenticator app as well.

Revision as of 14:57, 23 June 2022

The system uses a proprietary login, which usually consists of 2 steps:

1) From our website's home page, you log into your organisation, using an organisation name and password, which is shared by everyone in your organisation.

2) This takes you to your organisation's login page within the application, where you log in with your personal user name and password. Messages from your administrator, and/or Dizions, are displayed alongside the login form.

Long term, we are planning to replace this with a single sign-on process, which will enable you to log in using your Microsoft account, which will streamline credential management within your organisation.

To prepare for this change, for the October 2022 release, we are planning the following changes:

1) Each organisation will have access to their own login link, which can be used instead of step 1 above. Users can bookmark this link, or if you have an intranet, it could be placed somewhere prominent.

2) User records will be created by default with an email address instead of a separate user name. If you use the login link, all users must use an email address instead of a user name. Users who currently have a separate user name can continue using it with the 2 step login process.

3) For organisations concerned about the removal of the need for an organisation password, we'll be making two factor authentication easier. Currently it's available using SMS messages. We'll be adding an option to use an authenticator app as well.