Can't use HTTPS for localhost OAuth callback

Hey all,

Having some issue with the callback url for my OAuth flow. I get that non localhost callbacks require https, but what I’m seeing is that using a localhost seems to then require no https as this isn’t editable. How can I get around this?

To be clear I want my localhost callback to use https.

Hi @JSlowik

Are you still struggling with this? I believe you should be able to use either http or https when using localhost. Here is an announcement from some time ago where we opened it up to http (it used to be you had to use https for localhost).

@prosa , do you have any additional thoughts here?

Hey @Dennis yeah still an issue. I expected to be able to use either or for localhost given the post, however I note that in the app setup that’s not actually something I’m given control of. It seems to just default to http when using localhost, and if there’s an option to change it it isn’t immediately obvious to me.

Hi @JSlowik ,
Have you resolved this issue? If not then please try this “Screenshot by Lightshot”. If not solved then try with http to https
Hope this helps!
If we were able to answer your query, kindly help the community by marking it as a solution.
Thanks and Regards.

Hey @webdew, not sure if we got our wires crossed a bit or if this account is a bot (thinking a bot given the upvote?), in any case if you are a human you’ll note that you have the same config issue as I do. At the very least I appreciate confirmation I don’t have some browser addon breaking the UI.

In the interest of full disclosure I don’t need workarounds for my side. I simply add an ‘s’ when the http callback fails to load, and I’m utilizing refresh tokens so I don’t run into it a lot locally anyway. I think what happened is someone got a little overzealous after the HTTP/HTTPS requirement was implemented. It happens, but it’s a silly thing to have done imo, and I’m just a little disappointed.

Seem to have confirmed this is a UI error. Sent the app info update request myself and modified the request json to include https for localhost and now it’s working. @dennisedson I saw a community manager badge. Any chance you’re connected enough to escalate this (contacted support via twitter on Monday, but haven’t heard much back)? Thanks.

@JSlowik

Let’s see what that badge can do for us.

Out of curiousity, do you have a link to that tweet as well?

Hey @dennisedson as it happens I just got a reply from their support on Twitter this morning: Post / X

Is our best bet to wait and see what comes of that?

@JSlowik , will connect with him and see what is happening!

Thanks for the link :grin:

@JSlowik heads up, fix is being worked on. Anticipating a release to production today or tomorrow :grinning_face:

What a turnaround! That’s exciting. Thanks @dennisedson