Redirect URI for brokered OAuth on public clients (cannot use any previous answer > 6 mo. old)
Our MAUI production app has had a longstanding OAuth 2.0 flow, brokered by our organization’s server, that employed the now-deprecated Custom URI Redirect scheme after supplying secrets held on the server. The PKCE loopback scheme has also been deprecated and can’t be used either. My best-case migration scenario would be to broker this using the Firebase project that the MAUI apps are linked to.
Redirect URI for brokered OAuth on public clients (cannot use any previous answer > 6 mo. old)
Our MAUI production app has had a longstanding OAuth 2.0 flow, brokered by our organization’s server, that employed the now-deprecated Custom URI Redirect scheme after supplying secrets held on the server. The PKCE loopback scheme has also been deprecated and can’t be used either. My best-case migration scenario would be to broker this using the Firebase project that the MAUI apps are linked to.
Redirect URI for brokered OAuth on public clients (cannot use any previous answer > 6 mo. old)
Our MAUI production app has had a longstanding OAuth 2.0 flow, brokered by our organization’s server, that employed the now-deprecated Custom URI Redirect scheme after supplying secrets held on the server. The PKCE loopback scheme has also been deprecated and can’t be used either. My best-case migration scenario would be to broker this using the Firebase project that the MAUI apps are linked to.
Redirect URI for brokered OAuth on public clients (cannot use any previous answer > 6 mo. old)
Our MAUI production app has had a longstanding OAuth 2.0 flow, brokered by our organization’s server, that employed the now-deprecated Custom URI Redirect scheme after supplying secrets held on the server. The PKCE loopback scheme has also been deprecated and can’t be used either. My best-case migration scenario would be to broker this using the Firebase project that the MAUI apps are linked to.