OpenBankProject / OpenBankProject/OBP-API
Is it obligatory that a third party app uses liftweb ajax calls to perform the oauth lifecycle?
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 1.7k
- Forks
- 482
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 15
Description
This is an unusual question but i would really appreciate an answer. Is it obligatory that a third party app uses liftweb ajax calls to perform the oauth authorization lifecycle?
I would really like to create a third party app but i want the oauth authorization lifecycle to be executed without any liftweb ajax calls.
I mean is there another valid way that i can use to receive the oauth_token from the oauth provider web site etc other than a liftweb ajax call?
Thank you in advance for you time to enlighten me...
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
The issue mentions the OAuth authorization lifecycle and Liftweb AJAX calls but names no files, tests, or entry points. Start by locating the project’s OAuth flow, then document whether third-party clients can complete authorization without Liftweb AJAX calls and what supported flow applies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- api, authentication
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100