jy95 / keycloak-capacitor Goto Github PK

@jy95 - I wanted to ask why you used cordova-plugin-browsertab instead of cordova-plugin-inappbrowser.

browsertab doesn't offer any customizations of the browser interface, whereas inappbrowser does, and there is example of passing the caller-defined options into inappbrowser.open(...) in keycloak-js already.

Was it just a decision based on wanting to get something up and going quickly or was there a technical reason?

Android looks fine, but I've noticed on iOS that there are some undesirable elements of the browser interface that break the illusion that you're in a native app.. most egregious being the Share button and the Safari button in the bottom right that will open the url in external Safari. I can live with this, but it was some polish I was trying to clean up.

Thanks in advance for the info and history on it.

could you please add an example when work with ionic-react?. I face an issue when try to read angular code?

Question Question(s):

First, I'm accustomed to keycloak-angular on the web side of things and am wanting to create mobile app w/ ionic.
keycloak-angular provides a Service which you initialize up front as a provider.

This service provides several useful behaviors:

1. It automatically refreshes the token when needed
2. It automatically injects the Authorization header in HTTP requests (using angular's HttpInjector)
3. It remembers from instance to instance if the user is still logged in

Does keycloak-capacitor offer any of these automatic behaviors? Or, is it left up to the user to make the necessary call on the keycloak object to refresh the token, and set up our own HttpInterceptor, etc?

Thanks!

Would it be possible to upgrade the ng-example to the latest packages (e.g. capacitor) and latest keycloak? I too am using ionic w/ keycloak and this package. But I've upgraded my app's dependencies to the latest packages (including ionic v7) and something isn't working. I've re-created a minimal example and it's similarly not working.

The problem seems to be when keycloak redirects back to the app on iOS, using a custom URL scheme, that the app does get resumed, but it essentially ignores the query string information. At least the keycloak service doesn't indicate that the user is logged in upon returning back to the app. What part is supposed to notice that it came back to the app via the custom url scheme, there's a query string representing the state that must be used to obtain the refresh token, etc.?

My own example works when the adapter is "default" and I test in a browser, but when using the capacitor adapter and iOS, it does not.

I'm at a loss for the problem. I came here to try and run its example, but can't get it even to install the npm packages at this point.

Any help would be appreciated.