how to refresh token and access token from ios can used in web server?
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 2k
- Forks
- 867
- Avg merge
- 4d 48m
- Merged PRs (30d)
- 1
Description
this code when i used client id ios
`let kRedirectURI: String = "com.googleusercontent.apps.CLIENT_ID_IOS:/oauth2redirect";
let request = OIDAuthorizationRequest(configuration: configuration,
clientId: "CLIENT_ID_IOS.apps.googleusercontent.com",
scopes: [OIDScopeOpenID,OIDScopeProfile,"https://www.googleapis.com/auth/youtube","https://www.googleapis.com/auth/youtube.readonly"],
redirectURL: redirectURI,
responseType: OIDResponseTypeCode,
additionalParameters: nil)`
I got refresh token and access token. but not working when i calling my API in web
this is my code when i used client id web
`let kRedirectURI: String = "com.googleusercontent.apps.CLIENT_ID_IOS:/oauth2redirect"
let request = OIDAuthorizationRequest(configuration: configuration,
clientId: "CLIENT_ID_WEB.apps.googleusercontent.com",
clientSecret: CLIENT_SECRET
scopes: [OIDScopeOpenID,OIDScopeProfile,"https://www.googleapis.com/auth/youtube","https://www.googleapis.com/auth/youtube.readonly"],
redirectURL: redirectURI,
responseType: OIDResponseTypeCode,
additionalParameters: nil)`
I got an error "custom scheme URIs are not allowed for 'Web' client type"
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
No repository files or tests are named. Start with the OIDAuthorizationRequest configuration and the OAuth client and redirect URI settings shown in the issue; compare the iOS and web client requirements, then verify that the selected token flow produces credentials accepted by the web API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100