Please check the following problem and their solution:
What to do when Secude library is not found?
Please check whether the logged file exists and set the parameter snc/gssapi_lib correctly, if necessary. And check whether the access authorizations for the file are set so that the work process (as user ) can access the file.
What to do when No Secude Credential file with valid name found?
Below error message can be caused by two factors:
a) No cred file is found. During the Secude login (seclogin), a file "cred" is created. The Secude library searches for this file in the home directory of the
Take the Secude logon (seclogin call, see Secude documentation) and check whether the file exists at the correct point.
b) If the cred file exists at the correct point, the name which is entered in the profile parameter snc/identity/as does not correspond to the identity for which a logon was carried out with seclogin.
With "seclogin -l" check the identity of the user logged on for Secude. For snc/identity/as=, this identity must be entered (with the additional prefix "p:" .
snc/identity/as=p:CN=MyR3, OU=Production, O=SAP, C=DE
Identity in the cred file must be:
CN=MYR3, OU=Production, O=SAP, C=DE
What to do when PSE is not found?
During Secude login (seclogin) file "cred" was created. A PSE was also entered. The place (complete path name of the file or the directory) of the PSE is recorded in the cred file.
At the time of a logon, an attempt is made to access the PSE. However, either no PSE was to be found at the point specified or it could not be opened.
The problem occurs, for example, if an attempt was made to transport the cred file and the PSE to another point in the file system.
Using "seclogin -liters" check the path name under which the PSE is expected. The PSE must be contained there.
The easiest way to solve the problem is generally by making a new Secude logon.
You must find out, if necessary, why you cannot access the PSE indicated with "seclogin -l".
Getting an Errors in the Security Network Layer
What to do when Signature of a certificate cannot be checked?
The PSE (Personal Security Environment) of the user and application server are issued by different CAs (Certification Authorities). The PSE of the user does not contain a public key of a CA with which the certificate of the application server can be verified.
Use PSEs of the same CA. If this is impossible, check out the option of cross certification with Secude support.
We are getting Invalid PIN
The seclogin (that is, the creation of the cred file) might have been carried out for the application server under another UNIX or NT account (Userid) as that under which the R/3 application server is being operated.
The Secude seclogin must be carried out under the account of the adm.
Delete the cred file and carry out the seclogin again after logging on as adm.
What to do when No user with suitable SNC name exists?
Please Assign the SNC name to the respective R/3 user (Transaction SU01).
Why Validity period of the (application server) certificate has run out?
You can get your CA to create a new PSE for the application server or extend the validity period.