JumpCloud Failing to Login User

avatar

I just moved from our older Wayk Den server to a new Wayk Bastion server built from scratch on a new Ubuntu 18.04 server in Azure. Using my old parameters, I configured and deployed my URLs and enabled SSL like before and I see all 77 of our machines checking in and showing up. However, the ONLY user I can use is the wayk-admin user there by defaults. I repeated the JumpCloud setup steps a few times, and can confirm the right user and password appear in both the Get-WaykBastionConfig and in the web/settings/account-provider screen. My two users coming from JumpCloud show up on the user list, they are assigned licenses, and they have assigned roles (Owner) in Wayk Bastion. Is there something I'm missing? All functions and features seem good except for the LDAP login.

All Comments (11)

avatar

Hi,

If JumpCloud users show up on the user list, your configuration is good. So if my understanding is correct, when you try to use your JumpCloud user to login in Wayk Bastion, it doesn't work, am I right ?

Our login is done in two steps. You have to enter your username, press continue, than you enter your password. Can you tell me if you get an error message when you enter your username or when we validate the password ?

Sorry for inconveniences, I will try to reproduce it and let you know if I have something similar on my side.

Best regards,

François Dubois

avatar

Hi,

I just reproduced the issue on my side. I'm sorry about that. The good news is that we plan a new version next week. So a fix should be integrated in that version. Meanwhile, if you can't wait that new version, I would suggest that workaround :

Downgrade Wayk Bastion to version 2020.3.3. You have probably installed Wayk Bastion 2020.3.4 and that version introduced a the regression. Version 2020.3.3 had one issue fixed by 2020.3.4 and here it is : Fix an issue where user logged in Wayk Client was logged out every day. So you will have to log in every day in Wayk Client since the issue cause the token to be invalid after 24 hours. But other than that, it should work well.

Again, sorry for inconveniences, I will post again next week when the version will be available.

Best regards,

François Dubois

avatar

No problem. Is there a way to define the version? I don't see anything in the docs.

avatar

Hi,

You can run the Powershell command Get-InstalledModule WaykBastion to see the version installed. You can also see it in the Wayk Bastion web UI, Settings -> Sytem Information, you will see the Cmdlet Version.

To install a previous version, you can use that command : Install-Module -Name WaykBastion -RequiredVersion 2020.3.3

Don't hesitate if we can help with something else.

Best regards,

François Dubois

avatar

Hi,

Thank you for your patience. Wayk Bastion 2021.1.0 is now available, and it contains a fix for authentication with JumpCloud account. You should be able to use your JumpCloud account and log in Wayk Bastion.

Let us know if you have any further questions or problems.

Best regards,

François Dubois

avatar

I just upgraded but I am now getting 500 errors on login no matter which user I login as to the system. Both wayk-admin and my LDAP users fail. Is there a place to pull logs to find the cause?

avatar

Hi,

You can run that command

> docker logs den-server > den-server.log


And send me the den-server.log in a private message. Could you also send me the result of the command `docker ps` to see all containers.

Best regards,

François Dubois

avatar

Sent!

avatar

Hi,

Here is a conclusion of what we found after many exchanges in case it could help others.

#1 - You should never try to reach the login page by yourself, directly by adding `/lucid` at the end or your URL ( BastionUrl/lucid ). This will not forward you back to the application and you will have the feeling that the login didn't work. Instead, you have to reach your Bastion URL and it should forward you to the login page if you are not already logged in. If you are not forwarded properly, this is an issue.

#2 - We have an issue in Wayk Bastion 2021.1.0. If you have a system sending a request HEAD on your Bastion URL, it could be an issue. The best thing for now is to stop any system sending a HEAD request on that URL. We are working to fix that issue in next release.

Best regards,

François Dubois

avatar

Hi,

We released Wayk Bastion 2020.1.2 and that version fixes the issue with HEAD request. The server should be able to handle correctly those request.

Best regards,

François Dubois

avatar

Excellent, just upgraded and I'll run the monitoring script again to see if it has issues. Thanks!