w3c-fedid/idp-registration

Issues

• Social Web + Browsers = <3

  #15 opened 2 months ago by samuelgoto
  7

• Users can't use IdPs outside of the ones enumerated by RPs

  #2 opened 3 years ago by tplooker
  221

• Allow relative urls in the IdentityProvider.register() call

  #14 opened 2 months ago by samuelgoto
  0

• Allow RPs to provide their own terms of service and privacy policy URLs for "configURL: any" option

  #8 opened 8 months ago by aaronpk
  16

• Allow IdPs to return JSON objects rather than Strings back to RPs

  #13 opened 8 months ago by samuelgoto
  7

• Allow IdP registration and RPs to match on a "type"

  #1 opened 8 months ago by aaronpk
  100

• FedCM for Research and Education

  #12 opened 8 months ago by ekupris
  0

• Relax the mimetype check of the .well-known/web-identity file

  #11 opened 8 months ago by samuelgoto
  0

• Make it easier to deploy this at the eTLD+1 for registered IdPs

  #10 opened 7 months ago by aaronpk
  10

• Skip the .well-known check for Registered IdPs

  #4 opened 7 months ago by anderspitman
  34

• DNS option instead of well-known URI

  #9 opened 8 months ago by aaronpk
  7

• The Registration API: Remove the user gesture requirement behind `IdentityProvider.register()`

  #7 opened 8 months ago by samuelgoto
  7

• The Registration API: Consider not making requests to unknown login status

  #6 opened 8 months ago by cbiesinger
  7

• IdP Registration API: allow enumerating all registered `configURL`s

  #5 opened 8 months ago by samuelgoto
  7

• IdP Registration same-site v same-origin

  #3 opened 5 months ago by philsmart
  2