missing AccessToken response (IOS) about generic-oauth2 HOT 6 CLOSED

Are you sure that MS supports implicit flow for native apps? Please add the link to their docs.

Please debug into the plugin in XCode (search for the plugin class. It's there I debug that way myself) and see how far the call gets.

from generic-oauth2.

ms does support implicit flow ,

Im not using the plugin anymore ,

thanks

from generic-oauth2.

OK, but just out of curiosity. What do you use instead?

from generic-oauth2.

I am changing window location to

https://login.microsoftonline.com/{org-id}/oauth2/v2.0/authorize?client_id={AzureAD_APPID}&redirect_uri=http%3A%2F%2Fwebserverurl%3A8082&scope=user.readwrite&response_type=token&state=&prompt=login

then telling capacitor via cap.conf to allow redirection to ms loginpage inside "allowNavigation"
{ "server": { "url": "https://webserverurl.com", "allowNavigation": [ "sts.domain.dk", "login.microsoftonline.com" ] } }

then
I grab the token from the returned uri "/#access_token=*****" via

  parseTokenFromUrl(){
           const HashKeyValueParsed_JSON = {};
          window.location.hash.substring(1).split('&').forEach(function (x) {
            var arr = x.split('=');
            arr[1] && (HashKeyValueParsed_JSON[arr[0]] = arr[1]);
          });

removeHash(){
      let noHashURL = window.location.href.replace(/#.*$/, '');
      window.history.replaceState('', document.title, noHashURL)

currently I am not able to set the the redirectURI to a specific IOS app scheme as capacitor://localhost, capacitor just complaining inside the console that's it is not a valid https url

for now the app is just encapsulated inside IOS webView kind of PWA app,

I really want to use the plugin instead of having a webserver I will follow the task you created sorry because I closed it I did not know you are investigating and digging to resolve , I thugt I was alone here

/Ibrahim

from generic-oauth2.

Thanks for that. I hope to find some time to investigate further next weekend.

from generic-oauth2.

The original issue had nothing to do with fragment vs query response mode but with the fact that the plugin didn't return the access token, when no resourceUrl was configured.

This behavior will be introduced with version 2.0.0 of the plugin. see #75

from generic-oauth2.