dhis2-users team mailing list archive

[Jason Phillips <jason@xxxxxxxx>]

Greetings, community!



HISP SA is looking at ways to implement a single-sign-on solution within
our hosted DHIS2 instances, potentially using OAuth and a self-hosted
central OpenID/OpenAuth server entity (or even a dhis2 instance?) for
authentication.

Has anyone got any experience with implementing such a solution, and/or any
advice about what the best practice could/would be to do so?
The aim would be to try and get all dhis2 instances to share a single
user’s password across the board, and ideally be able to revoke, manage and
control access to all instances in a single location.



Any advice, comments, suggestions or guidance would be most welcome.



Kind Regards,

*Jason Phillips*

[image: hisp]
*Information Systems / Infrastructure*

*Health Information Systems Program____________________________________*

eMail:               jason@xxxxxxxx
Tel/Fax:            +27 21 712 0170
Cell:                 +27 72 973 7250
Skype:             jason.n.phillips

This message and any attachments are subject to a disclaimer published at
http://www.hisp.org/policies.html#comms_disclaimer.  Please read the
disclaimer before opening any attachment or taking any other action in
terms of this electronic transmission.  If you cannot access the
disclaimer, kindly send an email to disclaimer@xxxxxxxx and a copy will be
provided to you. By replying to this e-mail or opening any attachment you
agree to be bound by the provisions of the disclaimer.



[image: cid:image002.jpg@01D2F4CE.CFC9B9B0]

See the conference website <https://www.ehealthalive.org/> for more
information!

-- 


*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
<http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.  If you cannot access the 
disclaimer, kindly send an email to disclaimer@xxxxxxxx 
<disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.*