Security Guide > Security Guide > Implementing FIM > Debugging FIM Authentication
Was this helpful?
Debugging FIM Authentication
The FIM password authentication process can be verified by passing the username and password directly to the ingvalidacctkn script. On Unix or Linux perform this task as an example:
echo "username password" | ingvalidacctkn
echo $?
When $? shows 0, the username password combination is accepted. A value other than 0 signifies that the authentication failed. A combination of username and token can be verified similarly. In case of providing a token, it should have access_token= pre-pended.
echo "username access_token=token" | ingvalidacctkn
echo $?
You can trace the authentication by setting environment variables II_FIM_LOG to specify the full path to a trace file and II_FIM_TRACE to specify the trace level. The level can be set to 1 (warning), 2 (info) or 3 (debug). With level 3, the most detailed information is logged into the file.
Example
ingsetenv II_FIM_LOG /tmp/fim.log
ingsetenv II_FIM_TRACE 2
Note:  With trace level 3, the log file will contain sensitive information, for example, passwords and tokens in clear text.
Last modified date: 12/19/2024