kibana/x-pack/test/security_api_integration/ftr_provider_context.d.ts

/*
 * Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one
 * or more contributor license agreements. Licensed under the Elastic License
 * 2.0; you may not use this file except in compliance with the Elastic License
 * 2.0.
 */

import { GenericFtrProviderContext } from '@kbn/test';
import { services } from './services';

export type FtrProviderContext = GenericFtrProviderContext<typeof services, {}>;
Add OpenID Connect auth provider (#36201) The OpenID Connect authProvider is the accompanying authProvider for the OpenID Connect authentication realm in Elasticsearch. This is very similar to the saml authProvider in most ways with three noticeable differences: - We require explicit configuration regarding the Elasticsearch realm name instead of trying to build an environment aware string (like ACS URL in saml) and pass that to Elasticsearch for it to resolve the realm. - We do not support multiple values for the realm specific nonces (state and nonce) as we do with requestId in the SAML realm. Instead if an existing value ( for state and nonce) is present in the user's session, we pass that to Elasticsearch to be reused. The end goal is the same, allow a better UX for users attempting many requests over different tabs in the same browser context. - IDP initiated SSO ( Third Party initiated authentication in OIDC-speak ) is implemented but starts as an unsolicited request to initiate the handshake, instead of an unsolicited request with an authentication response (which is not supported here) This change also adds a fake plugin named oidc_provider to be used in integration tests for mocking calls to the token and userinfo endpoint of an OpenID Connect Provider This does not support the OpenID Connect Implicit flow as that depends on fragment handling/processing as described for instance in the spec Co-Authored-By: Brandon Kobel <kobelb@elastic.co> 2019-05-21 19:23:27 +02:00			`/*`
			`* Copyright Elasticsearch B.V. and/or licensed to Elasticsearch B.V. under one`
Elastic License 2.0 (#90099) * Updating everything except the license headers themselves * Applying ESLint rules * Manually replacing the stragglers 2021-02-04 03:12:39 +01:00			`* or more contributor license agreements. Licensed under the Elastic License`
			`* 2.0; you may not use this file except in compliance with the Elastic License`
			`* 2.0.`
Add OpenID Connect auth provider (#36201) The OpenID Connect authProvider is the accompanying authProvider for the OpenID Connect authentication realm in Elasticsearch. This is very similar to the saml authProvider in most ways with three noticeable differences: - We require explicit configuration regarding the Elasticsearch realm name instead of trying to build an environment aware string (like ACS URL in saml) and pass that to Elasticsearch for it to resolve the realm. - We do not support multiple values for the realm specific nonces (state and nonce) as we do with requestId in the SAML realm. Instead if an existing value ( for state and nonce) is present in the user's session, we pass that to Elasticsearch to be reused. The end goal is the same, allow a better UX for users attempting many requests over different tabs in the same browser context. - IDP initiated SSO ( Third Party initiated authentication in OIDC-speak ) is implemented but starts as an unsolicited request to initiate the handshake, instead of an unsolicited request with an authentication response (which is not supported here) This change also adds a fake plugin named oidc_provider to be used in integration tests for mocking calls to the token and userinfo endpoint of an OpenID Connect Provider This does not support the OpenID Connect Implicit flow as that depends on fragment handling/processing as described for instance in the spec Co-Authored-By: Brandon Kobel <kobelb@elastic.co> 2019-05-21 19:23:27 +02:00			`*/`

[kbn/test] move types/ftr into src (#99555) * [kbn/test] move types/ftr into src * Apply eslint updates * fix import of Lifecycle type Co-authored-by: spalger <spalger@users.noreply.github.com> Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com> 2021-05-17 18:51:53 +02:00			`import { GenericFtrProviderContext } from '@kbn/test';`
Implement Server-Side sessions (#68117) 2020-08-18 08:38:23 +02:00			`import { services } from './services';`

			`export type FtrProviderContext = GenericFtrProviderContext<typeof services, {}>;`