Updated README and TODO files to reflect the current state of the
project.
This commit is contained in:
@@ -326,7 +326,19 @@ CONFIGURING ADDITIONAL IDENTITY TOKEN PROVIDERS
|
||||
|
||||
SECURITY CONSIDERATIONS
|
||||
|
||||
- TBD -
|
||||
The ATS runs over Tomcat and by default receives requests over HTTPS on port 2645. For ease
|
||||
of use, the basic ATS setup scrip creates a self-signed certificate to be used by SSL. The
|
||||
use of self-signed certificates weakens the security properties of the SSL channel by forcing
|
||||
clients to accept them. At this time, the default mode for auth_token clients is to allow
|
||||
self signed-certificates. It is recommended that administrators obtain a certificate signed
|
||||
by the appropriate authority and configure the ATS to use it and change the auth_token client
|
||||
configuration to not accept invalid certificates to avoid this issue.
|
||||
|
||||
CASA Authenticatication Tokens when compromised can be used to either impersonate
|
||||
a user or to obtain identity information about the user. Because of this it is
|
||||
important that the tokens be secured by applications making use of them. It is
|
||||
recommended that the tokens be transmitted using SSL.
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user