Add section in the "Implementation Advice" document about supporting Mobile Apps
Open
@davidgtonge is already working on this.
Since Jul 11, 2026.
component: Implementation & Deployment Advice
migrated-from-bitbucket
priority: major
type: enhancement
- Dominant language
- HTML
- Stars
- 3
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
Originally submitted by dgtonge (Dave Tonge) on 2019-07-31
We discussed on the call adding a section around supporting mobile apps on auth journeys.
My suggestion would be that this section mentions:
- FAPI RW supports mobile apps using standard OAuth based redirects using claimed HTTPS scheme
- Some details on how claimed https works - with Apple / Android specific instructions
- Specific recommendations on how user agents for RPs can support both claimed https and normal https links with the best user experience (this is not easy!!!)
- Recommendations on how to support multiple brands (e.g. multiple discovery docs…)
- Explanation of the use-cases where FAPI-CIBA is applicable and any implementation considerations
Bitbucket status: open
Bitbucket origin: issue 260
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.