Clarifying disconnected services
This commit is contained in:
@@ -10,8 +10,9 @@ We use [file:///etc/openldap/users.d](a users.d) folder to hold the default user
|
|||||||
|
|
||||||
# Available Clients
|
# Available Clients
|
||||||
Most services on AniNIX, ranging from SSH & IRC to web services like AniNIX/Foundation and AniNIX/Singularity, are LDAP clients. Our exceptions are below:
|
Most services on AniNIX, ranging from SSH & IRC to web services like AniNIX/Foundation and AniNIX/Singularity, are LDAP clients. Our exceptions are below:
|
||||||
* MediaWiki (LDAP dropped out of support)
|
* MediaWiki (LDAP dropped out of support, but for a specific user.)
|
||||||
* AniNIX/Superintendent (client path not yet identified)
|
* AniNIX/Superintendent (client path not yet identified -- minor, as this is like minting a physical key)
|
||||||
|
* AniNIX/Singularity (app integration needs long-running credential to avoid user lockouts).
|
||||||
|
|
||||||
# Equivalents or Competition
|
# Equivalents or Competition
|
||||||
Both Google and Facebook offer distributed authentication systems. Google in particular is a good equivalent, as some of the services used by this network rely on its authentication for various products it provides internally.
|
Both Google and Facebook offer distributed authentication systems. Google in particular is a good equivalent, as some of the services used by this network rely on its authentication for various products it provides internally.
|
||||||
|
|||||||
Reference in New Issue
Block a user