Issue: The following error is reported while doing a test connection after configuring SNC for SAP adapter.

Error String
1). GSS-API(maj): No credentials were supplied
Unable to establish the security context

or

2).SS-API(min): SECUDE PSEDIR directory not found: C:\sec (Default)

or

3).GSS-API(maj): No credentials were supplied
GSS-API(min): No credentials found for this name (not logged on) (USER='OS user name')

or

4). GSS-API(maj): No credentials were supplied
GSS-API(min): File is not existing

Cause:

In order to access any PSE, the SAP adapter will proceeds as follows:
 
1). Read the environment variable SECUDIR.

2). If the credentials file "cred_v2" is found in the directory indicated by SECUDIR, continue with step 5.
 
3). If there is no credentials file but the PSE itself is found in SECUDIR and the PSE is not encrypted, open the PSE. The procedure finishes here. 

4). Else, an error message is thrown. 

5). On UNIX systems, check the environment variable USER for the name of the active user. 

6). Search in the file "cred_v2" for a credential for the PSE to be accessed. If there is no credential, an error message is thrown.

7)). Is the found credential readable for the active user? If not, an error message is thrown. 

8). Use the credentials to access the PSE. If the PIN does not match or the PSE is not found at the place specified in the credentials, an error message is thrown. 

9). Else, the PSE is opened successfully.

An error or warning message is issued if:

- The environment variable SECUDIR is not set correctly in the adr3_env.sh .
- The environment variable USER is not set correctly (on UNIX systems only).
- File "cred_v2" is not found in the directory specified in SECUDIR.
- File "cred_v2" does not contain credentials for the PSE to be accessed.
- The credentials found in "cred_v2" for the PSE are not readable for the active user.
- The PSE is not found at the place that is indicated by the credentials.
- The PIN provided by the credentials differs from the PIN used to encrypt the PSE.
- No location for the PSE and credentials has been defined.
- The certificates on the client and server side has not been configured properly. (This is in case if you are using an individual PSE).

All

Check or verify that:

- The environment variable SECUDIR is correctly set for the active user in adr3_env.sh . The Active user is the user who is going to execute the adapter from the adapter machine.

- On UNIX systems, the environment variable USER is correctly set for the active user.

- The container file for credentials "cred_v2' is found in the directory indicated by SECUDIR.

- A readable credential exists for the active user for the PSE in question.

- The credential contains the correct PIN (password). Note that the actual PIN can never be displayed. If the PIN contained in the credentials is wrong, you need to replace these credentials. Make certain that once set, a PIN is not forgotten.

- In case you are using an individual PSE, ensure that the certificates have been configured/provided properly on both the server and client side.

- On Windows system, if the adapter is running in the Administrator or as Windows service, please make sure the user 'SYSTEM' is granted to use pse in the cred_v2 file. 

Getting "No credentials were supplied" error after configuring SNC for SAP Adapter.