How it works In a traditional OpenID relying party interface, the RP implements a UI, and two endpoints on its server for processing OpenID related stuff: /openid_start - this endpoint accepts an openid_identifier parameter which is then ingested by an OpenID library to find out which provider is used by the identifier and make a secure association with the server. /openid_finish - the openid.retu
{{#tags}}- {{label}}
{{/tags}}