MaikuB / MaikuB/flutter_appauth
PlatformException(authorize_and_exchange_code_failed, Failed to authorize: Connection error making token request to 'https://xxx/realms/AAA/protocol/openid-connect/token': The certificate for this server is invalid. You might be connecting to a server that is pretending to be 'xxx' which could put your confidential information at risk...
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 308
- Forks
- 301
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 5
Description
Hi to Flutter app auth team.
I'm using the last version of flutter_appauth to connect with Keycloak server. Everything are working well, but I got an error when callback in IOS(it's working fine on Android).
`PlatformException(authorize_and_exchange_code_failed, Failed to authorize: Connection error making token request to 'https://xxx/realms/AAA/protocol/openid-connect/token': The certificate for this server is invalid. You might be connecting to a server that is pretending to be 'xxx' which could put your confidential information at risk...`
For iOS in info.plist:
`CFBundleURLTypes
CFBundleTypeRole
Editor
CFBundleURLSchemes
`
Maybe it's problem from self-signed certificate. How could I solve this problem?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the iOS callback and token exchange described in the issue, then inspect the Info.plist URL-scheme configuration and the iOS-side certificate handling in flutter_appauth. Reproduce the failure against the Keycloak endpoint and document a supported resolution that preserves certificate validation; done means the iOS exchange succeeds without weakening trust checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter, ios
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100