Client External View The FcsClient library does not interact directly with the user. Therefore, the user application, which uses FcsClient, is responsible for gathering the appropriate credentials from the user.

Server External ViewFor server-to-server interactions, authentication is the only network security method that is supported. SSO is not supported. At an MCS/FCS server, user interaction is absent and credentials must be provided programmatically. System administrators can either use the out-of-the-box authentication management or implement their own custom authentication management by providing the java.net.authenticator class.

Client Internal ViewThe client internal view comprises SSO or authentication.

Server Internal View
- SSO: Not supported in this view
- Authentication:
- Custom Authentication Management
- Out-of-the-Box (OOTB) Authentication Management
- Without Encryption: OOTB authentication management can be implemented without encryption by putting the credentials file in place and setting MX_HTTPDEFAULTCLIENTAUTHENTICATION to true.
0. At startup time, the credentials file is retrieved.
1. Upon receiving an authentication challenge, FCS first extracts the challenge information.
2. Then using that information, it obtains the appropriate credential.
3. Finally, it sends the credential out for authentication.
- With Encryption: OOTB authentication management can be implemented with encryption as follows:
-1. After running MxEncryptCredentials.class with the credentials files (and MX_HTTPDEFAULTCLIENTAUTHENTICATION and MX_ENCRYPTNETWORKCREDENTIALS both set to true), the encrypted credentials file is generated.
0. At startup time, the credentials file is retrieved and decrypted.
1. Upon receiving an authentication challenge, FCS first extracts the challenge information.
2. Then using that information, it obtains the appropriate credential.
3. Finally, it sends the credential out for authentication.

|