issues
search
w3c-fedid
/
idp-registration
A proposal to extend FedCM to allow RPs to accept "any" registered IdP
4
stars
0
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Social Web + Browsers = <3
#15
samuelgoto
opened
3 weeks ago
7
Allow relative urls in the IdentityProvider.register() call
#14
samuelgoto
opened
3 weeks ago
0
IdP Registration same-site v same-origin
#3
philsmart
opened
3 months ago
2
Make it easier to deploy this at the eTLD+1 for registered IdPs
#10
aaronpk
opened
5 months ago
10
Skip the .well-known check for Registered IdPs
#4
anderspitman
opened
5 months ago
34
IdP Registration API: allow enumerating all registered `configURL`s
#5
samuelgoto
opened
5 months ago
7
The Registration API: Consider not making requests to unknown login status
#6
cbiesinger
opened
6 months ago
7
The Registration API: Remove the user gesture requirement behind `IdentityProvider.register()`
#7
samuelgoto
opened
6 months ago
7
Relax the mimetype check of the .well-known/web-identity file
#11
samuelgoto
opened
6 months ago
0
Allow IdP registration and RPs to match on a "type"
#1
aaronpk
opened
6 months ago
100
Allow RPs to provide their own terms of service and privacy policy URLs for "configURL: any" option
#8
aaronpk
opened
6 months ago
16
DNS option instead of well-known URI
#9
aaronpk
opened
6 months ago
7
Allow IdPs to return JSON objects rather than Strings back to RPs
#13
samuelgoto
opened
6 months ago
7
FedCM for Research and Education
#12
ekupris
opened
6 months ago
0
Users can't use IdPs outside of the ones enumerated by RPs
#2
tplooker
opened
2 years ago
221