Pavel Borzenkov ab06119431 connector: implement LinkedIn connector ... connector/linkedin implements authorization strategy via LinkedIn's OAuth2 endpoint + profile API. It doesn't implement RefreshConnector as LinkedIn doesn't provide any refresh token at all (https://developer.linkedin.com/docs/oauth2, Step 5 — Refresh your Access Tokens) and recommends ordinary AuthCode exchange flow when token refresh is required. Signed-off-by: Pavel Borzenkov <pavel.borzenkov@gmail.com>		2017-10-27 12:54:28 +03:00
..
internal	*: revendor and regenerate protobuf files	2017-04-13 11:35:41 -07:00
api.go	server: fix panic caused by deleting refresh token twice through api	2017-09-05 23:56:34 -07:00
api_test.go	server: fix panic caused by deleting refresh token twice through api	2017-09-05 23:56:34 -07:00
doc.go	initial commit	2016-07-26 15:51:24 -07:00
handlers.go	Implement the “authproxy” connector (for Apache2 mod_auth etc.)	2017-10-25 21:53:51 +02:00
handlers_test.go	*: update go-oidc and use standard library's context package	2017-03-08 10:33:19 -08:00
oauth2.go	Cross clients improvement - requesting client ID always added to the audience claim	2017-09-28 18:30:15 +02:00
oauth2_test.go	server: fix localhost redirect validation for public clients	2017-05-09 17:09:20 -07:00
rotation.go	: update {S->s}irupsen/logrus	2017-07-25 13:46:44 -07:00
rotation_test.go	: update {S->s}irupsen/logrus	2017-07-25 13:46:44 -07:00
server.go	connector: implement LinkedIn connector	2017-10-27 12:54:28 +03:00
server_test.go	Cross clients improvement - requesting client ID always added to the audience claim	2017-09-28 18:30:15 +02:00
templates.go	{web,server}: use html/template and reduce use of auth request ID	2017-02-02 11:11:00 -08:00
templates_test.go	*: add theme based frontend configuration	2016-11-30 17:20:21 -08:00