Prashant,
On windows login:
If you prefer to use the obf-client-secret, you can generate the obfuscated value using the obfuscate.exe utility provided in the installation directory.
The first part of the Windows Login is done against the local machine (or AD) so all users must exist there as well as in the Verify cloud directory.
On Linux login:
I'm not sure why you would get a permission denied error from the token endpoint. To me that would indicate a bad host, client ID or secret. The configuration is quite simple so should be easy to check. The top of the configuration has this format:
{
"ibm-auth-api":{
"client-id":"xxxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"client-secret":"xxxxxxxxxx",
"protocol":"https",
"host":"xxxx.verify.ibm.com",
"port":"443",
"authd-port":12,
"max-handles":"16"
},
Make sure you have set the host, client-secret, and client-id correctly. When I set up SSH I had to make a change to SELinux policy to allow the sshd process to communicate on port 12 (where the verify daemon is listening). I also had to modify the sshd configuration to allow for multi-step authentication. I did cover all of this in my MFA Everywhere cookbook.
When you say you called the token endpoint via cURL, did you send the client-id and secret and successfully get back an Access Token? If so, then I can't explain the issue... perhaps you will need to open a support case.
Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------
Original Message:
Sent: Wed September 02, 2020 02:07 AM
From: Prashant Narkhede
Subject: Cloud Identity "MFA Everywhere" cookbook
Hi Jon,
I have checked the configurations again and observed that I am using obf-client-secret. I guess this needs additional encryption using some tool. So changed it to client-secret and 2FA with windows login worked for me. However, I had to create demouser on the windows machine as a local user.
For, 2FA for Linux SSH, I have turned on the logs and observed permission denied error while calling v1.0/endpoint/default/token endpoint from the Linux machine.
I have enabled all for the MFA-Client created in CI. Also, tried to call the token endpoint from the same Linux machine via CURL and it's working fine.
I think I am missing something in the configuration. Can you please guide me on this?
------------------------------
Prashant Narkhede
Original Message:
Sent: Wed August 26, 2020 10:11 AM
From: Jon Harry
Subject: Cloud Identity "MFA Everywhere" cookbook
Prashant,
I can't tell what the issue is from information provided. Both Windows Login and PAM login have ability to write a trace log. You should turn that on and see if these logs give a clue on the problem. If not, post here and hopefully it can help with debug.
For Windows issue, not seeing the Verify login option means the credential provider didn't initialise correctly. This is likely related to a configuration issue. Maybe provide your config here (with keys redacted). Creation of demouser is not required to see the credential provider option so that is not the issue.
For SSH issue, make sure the SSHD configuration has been updated to allow multi-step login - and that sshd Service has been restarted after change.
Jon.
P.S. I am on vacation this week. I will only be checking the forum infrequently.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
Original Message:
Sent: Wed August 26, 2020 07:04 AM
From: Prashant Narkhede
Subject: Cloud Identity "MFA Everywhere" cookbook
Hi Jon,
Thank you for the cookbook.
I am configuring the IBM Verify Gateway for Windows Login. For this, I am using Windows Server 2016.
I did the configurations suggested in the cookbook.
However, the issue I am facing is that I am not able to see any Sign in options on the Windows Login screen. I checked the configurations again but those look fine to me.
The other question is do I need to create demouser as windows local user. I tried with and without the user but it didn't help.
I progressed with other use cases for IBM Verify Gateway for PAM and facing issues for that too.
The commands are configurations have been completed successfully but when accessing Linux machine using ssh it is repeatedly prompting for the password.
Also, after the configurations, the SSH access to root has been blocked even root is member of nomfa group.
Can you please help me with this?
------------------------------
Prashant Narkhede
Original Message:
Sent: Tue September 03, 2019 05:32 AM
From: Jon Harry
Subject: Cloud Identity "MFA Everywhere" cookbook
Hello All,
My "Multi-Factor Everywhere with Cloud Identity" cookbook has just been published on the Security Learning Academy. This cookbook explores the new Cloud Identity Gateways for Windows Login, *IX PAM, and RADIUS.
You can access the cookbook here.
Cheers... Jon.
------------------------------
Jon Harry
Consulting IT Security Specialist
IBM
------------------------------