dex/static/fixtures/connectors.json.sample

[
	{
		"type": "local",
		"id": "local"
	},
	{
		"type": "oidc",
		"id": "google",
		"issuerURL": "https://accounts.google.com",
		"clientID": "${CLIENT_ID}",
		"clientSecret": "${CLIENT_SECRET}"
	},
	{
		"type": "github",
		"id": "github",
		"clientID": "${CLIENT_ID}",
		"clientSecret": "${CLIENT_SECRET}"
	},
	{
		"type": "bitbucket",
		"id": "bitbucket",
		"clientID": "${CLIENT_ID}",
		"clientSecret": "${CLIENT_SECRET}"
	},
	{
		"type": "ldap",
		"id": "ldap",
		"host": "127.0.0.1:389",
		"useTLS": true,
		"useSSL": false,
		"skipCertVerification": false,
		"baseDN": "ou=People,dc=example,dc=com",
		"nameAttribute": "cn",
		"emailAttribute": "mail",
		"searchBeforeAuth": true,
		"searchFilter": "(mail=%u)",
		"searchScope": "one",
		"searchBindDN": "searchuser",
		"searchBindPw": "supersecret",
		"bindTemplate": "uid=%u,%b"
	}
]
*: move original project to dex 2015-08-18 05:57:27 +05:30			`[`
			`{`
			`"type": "local",`
*: load password infos from users file in no-db mode not connectors In --no-db mode, load passwords from the users file instead of the connectors file. This allows us to remove the password infos field from the local connector and stop loading them during connector registration, a case that was causing panics when using a real database (see #286). Fixes #286 Closes #340 2016-04-05 06:35:00 +05:30			`"id": "local"`
*: move original project to dex 2015-08-18 05:57:27 +05:30			`},`
			`{`
			`"type": "oidc",`
			`"id": "google",`
			`"issuerURL": "https://accounts.google.com",`
			`"clientID": "${CLIENT_ID}",`
			`"clientSecret": "${CLIENT_SECRET}"`
static, server: add styles for github and bitbucket connectors Add icons and styles for github and bitbucket buttons. 2015-12-08 23:50:13 +05:30			`},`
			`{`
			`"type": "github",`
			`"id": "github",`
			`"clientID": "${CLIENT_ID}",`
			`"clientSecret": "${CLIENT_SECRET}"`
			`},`
			`{`
			`"type": "bitbucket",`
			`"id": "bitbucket",`
			`"clientID": "${CLIENT_ID}",`
			`"clientSecret": "${CLIENT_SECRET}"`
connector: add LDAP connector Authentication is performed by binding to the configured LDAP server using the user supplied credentials. Successfull bind equals authenticated user. Optionally the connector can be configured to search before authentication. The entryDN found will be used to bind to the LDAP server. This feature must be enabled to get supplementary information from the directory (ID, Name, Email). This feature can also be used to limit access to the service. Example use case: Allow your users to log in with e-mail address instead of the identification string in your DNs (typically username). To make re-use of HTTP form handling code from the Local connector possible: - Implemented IdentityProvider interface - Moved the re-used functions to login_local.go Fixes #119 2015-11-11 01:08:40 +05:30			`},`
			`{`
			`"type": "ldap",`
			`"id": "ldap",`
clean up LDAP connector * Remove some unlikely to be used fields to help configurability. * Combined "serverHost" and "serverPort" into "host" * Remove "timeout" (just default to 30 seconds). * Remove "maxIdleConn" will add it back if users feel the need to control the number of cached connections. * Remove "trustedEmailProvider" (just always trust). * Remove "skipCertVerification" you can't make this connector ingore TLS errors. * Fix configs that don't search before bind (previously broken). * Add more examples to Documentation * Refactor LDAPPool Acquire() and Put() into a Do() function which always does the flow correctly. * Added more comments and renamed some functions. * Moved methods on LDAPIdentityProvider to the LDAPConnector 2016-06-22 05:11:04 +05:30			`"host": "127.0.0.1:389",`
connector: add LDAP connector Authentication is performed by binding to the configured LDAP server using the user supplied credentials. Successfull bind equals authenticated user. Optionally the connector can be configured to search before authentication. The entryDN found will be used to bind to the LDAP server. This feature must be enabled to get supplementary information from the directory (ID, Name, Email). This feature can also be used to limit access to the service. Example use case: Allow your users to log in with e-mail address instead of the identification string in your DNs (typically username). To make re-use of HTTP form handling code from the Local connector possible: - Implemented IdentityProvider interface - Moved the re-used functions to login_local.go Fixes #119 2015-11-11 01:08:40 +05:30			`"useTLS": true,`
			`"useSSL": false,`
			`"skipCertVerification": false,`
			`"baseDN": "ou=People,dc=example,dc=com",`
			`"nameAttribute": "cn",`
			`"emailAttribute": "mail",`
			`"searchBeforeAuth": true,`
			`"searchFilter": "(mail=%u)",`
			`"searchScope": "one",`
			`"searchBindDN": "searchuser",`
			`"searchBindPw": "supersecret",`
			`"bindTemplate": "uid=%u,%b"`
*: move original project to dex 2015-08-18 05:57:27 +05:30			`}`
			`]`