Navigation
Single Sign On Development - .NET image 1

Single Sign On Development - .NET

JavaScript API Integration Java .NET Framework Web Application SQLite Business with 1-9 Employees

.NET Web Application API Integration Java SQLite JavaScript

My career must make a change in the way in which user identity is handled, along with the authorisation
process, and the way in which multiple
Licence access for individuals and organisations is handled.

To that end, the process would be to add a tab or similar to the current login page at
(link removed)

This would have a drop-down menu to select currently enabled libraries - these would be treated as a
School, for the purposes of data structures, was created by MyCareers staff.

Each library would need to have a set of associated API/Config details stored either in the SQL database
or the Azure Secrets Manager in order to configure how and where the call is made to the relevant
library.

The user would then enter the Library Card Identifier and associated PIN. Once verified, create a user in
the database and associate them with the school.
All other functionality remains the same.

Further information on this feature can be found in the specification document provided by My Careers.

At a high level, the required changes for the Library Single Sign-On feature are as follows:

● Front-end development
● Library authentication (SIP2) API details database schema/table
● Flexible library authentication API functionality/classes
● Linking/Creating an authenticated library account with internal My Careers accounts
● Integrating frontend & backend code
● Testing and Documentation
● Deployment

JavaScript API Integration Java .NET Framework Web Application SQLite Business with 1-9 Employees
Back to Portfolio