I am in exactly the same situation as the poster, so I will not explain it in detail as I’d be just repeating the same. But to keep it short, I’d like to implement login in my desktop app following the current best practices as described in RFC 8252 “OAuth 2.0 for Native Apps”. However that absolutely requires that the port can be specified at the time of the request, as the port can be different each time based on which are available in the client machine.
In the post linked above, you said a feature request was created for the support of “wildcards” for ports in the configured callback URLs. Apparently it’s not supported yet, though (or at least it’s not documented).
Is this something you plan to implement? Can I somehow follow the status of that request?
Thanks for taking the time to answer! According to my own testing, the star symbol does work as a wildcard for subdomains, so that a single entry in the “Allowed Callback URLs” will allow multiple subdomain.
It does not work, however, as a wildcard for the port, which is what this situation would require. If I attempt to save an entry with a “wildcard port”, such as “https://www.example.com:*/my-page” the dashboard will not even allow me to save it as it’s not a valid URI.