HTTPS callback support
Some OAuth providers require an https:// callback URL. TMS FNC Cloud Pack starts a local callback server during OAuth flows, and supports HTTPS callbacks for services that require them.
WEB applications
For TMS WEB Core applications, an HTTPS callback URL means the application must be deployed to an HTTPS server. The callback flow remains the same, but local browser testing over plain HTTP is not enough when the provider requires HTTPS.
Windows, Linux, macOS, and Android
For desktop and Android applications, TMS FNC Cloud Pack extracts the required self-signed certificates to a temporary folder and loads the OpenSSL libraries from the packaged resources. In debug builds, the HTTPS server can raise an SSL exception during the callback process; continue through the exception to complete authentication. Release builds do not show that debug exception.
iOS
For iOS device builds, the linker must be able to find libCrypto.a and libSSL.a from the product's HTTPS Support folder. Copy the libraries into the main source folder or add the support folder to the iOS 64-bit device library path in the IDE.
If the linker reports the known iOS library issue, add -V- to the project's additional parameters. See RSP-37075.
Customizing the callback server
Use OnConfigureHTTPServer to customize the local callback server. Use OnConfigureHTTPServerSSLHandler when the SSL handler needs custom settings.