By: Ha Ro user 07 Jun 2020 at 5 p.m. CDT

5 Responses
Ha Ro gravatar
Gluu 4.1.0 final on Ubunutu 18.04. Expected: URL string for OAuth has client id in the url matching the client id in the system. Instead the last 2 digits of the clientid are zeros, flow breaks due to not matching the clientid expected by the Idp. If manually correct those in the web browser url with the correct 2 digits, then flow proceeds. Example: Setup client in Gluu with Client ID: 714526522303578173 User arrives at login screen: Clicks the login link: https://discord.com/api/oauth2/authorize?response_type=code&client_id=714526522303578100&redirect_uri=https%3A%2F%2Fp1.rpgr.org%2Fpassport%2Fauth%2FGluuDiscordOAuth2-8173%2Fcallback&scope=openid%20identify&state=XgQGvIFpv5qvRiLkmMY1qPZU Notice that the client_id in the url is 714526522303578100 rather than 714526522303578173. I am getting this with every client I setup in the Passport Providers form Any ideas? Is this a bug, or something I'm doing wrong or misconfigured server? Thanks.

By Michael Schwartz staff 07 Jun 2020 at 9:02 p.m. CDT

Michael Schwartz gravatar
Wack....

By Ha Ro user 08 Jun 2020 at 8:39 a.m. CDT

Ha Ro gravatar
?

By Chris Eland staff 15 Jun 2020 at 8:24 a.m. CDT

Chris Eland gravatar
Hello Ha Ro, I'm gonna check this out

By Jajati Badu Account Admin 23 Jun 2020 at 10:13 a.m. CDT

Jajati Badu gravatar
I had also experienced the same issue. So when the IDP client_id is completely numeric. Passport js / Node try to roundup hence the client_id get changed. As an work around when you can hardcode the client id at the strategy .

By Ha Ro user 26 Jun 2020 at 8:42 a.m. CDT

Ha Ro gravatar
Thank you for the suggestion @jajati. I will see if I can make that work. @Chris.Eland Please let me know, since it appears from Jajati's comment that I'm not the only one, if you figure out a better fix. Thanks kindly! I'll report back later after I have had a chance to fiddle with the suggestion from Jajati.