openid / openid/AppAuth-iOS

Validating SSL Certificates via a Trust Store !

Open
#424 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
Objective-C
Stars
2k
Forks
867
Avg merge
4d 48m
Merged PRs (30d)
1

Description

This in particular to an issue that we are facing currently. The OAuth Provider's SSL Certificates received is probably ill formed when received by the SDK, as in only the leaf node(domain) that is received after a curl command instead of the entire chain.

However , this setup is in a development environment and the SSL Certs applied on the domain aren't public certs by the Certificate Authority but Internal Bank issued Certs (Root, Intermediate, Domain) that are put in keychain and simulators trust store. My queries are around the following

  1. Does AppAuth necessary depend on a valid public cert installed on OAuth Provider portal instead of internal bank issued certs
  2. Also does AppAuth SDK considers validating of the certs that have been manually installed on the simulator only.?

Im ask particular considering the limited knowledge on SSL Certs and validation within :)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by reviewing AppAuth-iOS's certificate-handling behavior for OAuth provider connections, then compare it with the internal Root, Intermediate, and Domain certificates installed in the keychain and simulator trust store. Done means documenting whether internal certificates and manually installed simulator trust certificates are supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, objective-c
Domain
authentication, mobile-dev, security
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.