NOT DONE WRITING
Hearing Health Care Industry Common Identity Services
<Brief description of what it is. Consider using an analogy to using your Linkedin Account.
- Single sign on for web based applications but more
- <not
<Will authenticate that an individual logging in as fjones@email.com is the authorized user of fjones@email.com. This user will be challenged to authenticate this by means such as:
- entering in a correct password
- using a MFA device/system (app, hardware)
- can be updated overtime to move with the changing times
The identity service will not go further to in other ways validate that Frank Jones using fjones@email.com is really Frank Jones
A HCB makes use of another Identity Service such as MS Active Directory or Azure Active Directory that meats the needs of a large enterprise setup, HIMSA's identity service will be able to integrate with that other system.
<Using IT industry standards and best practices for the implementation
Directory Features
The identity service will also provide for the storage of basic information about the HCB, its offices (address and location name) as well as basic information about the employees that make use of the Identity service
How HIMSA will use the Identity Service
Service Apps are applications that can come in many forms, web sites/portals, order applications etc. Noah ES is also a service app, an application that provide data hosting and other related services. When HCB's sign up for Noah ES they are also seamlessly creating and identity account as well. When logging into Noah ES the user will be authenticated by the HIMSA identity service
<AS the ID world gets more complicated the IdP can be made to meet these challenges while not impacting the members, the user benefits are also nice, this alllows the members to implement different systems by making it easier the user to have a smoother experience.>
How HIMSA Members may use the Identity Service
<could be used as a replacement to their current login systems or as an option>
<really need a simple example - logs into Noah ES, security token is established on the device (PC) from Noah or from outside of noah goes to web site and the service obtains security token and gets the user into acvity witout stopping to provide authorizaiton
<Make a point that their app is still completely in charge of authorizing what HCP's are able to do in their application>
- how the identity is linked and used by a service provider,
- the pros are that IdP is controlled by the industry, it is closed to members, can protect them from needing to integrate with other systems such as AD, AAD, etc.