IdentityProviderConfigurationProperty Struct
The identity provider configuration selected when the data store was created.
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { aws_healthlake as healthlake } from 'aws-cdk-lib';
const identityProviderConfigurationProperty: healthlake.CfnFHIRDatastore.IdentityProviderConfigurationProperty = {
authorizationStrategy: 'authorizationStrategy',
// the properties below are optional
fineGrainedAuthorizationEnabled: false,
idpLambdaArn: 'idpLambdaArn',
metadata: 'metadata',
};
Properties
authorizationStrategystringauthorization_strategystrauthorizationStrategyStringAuthorizationStrategystringAuthorizationStrategy*stringrequired#notes
HealthLake provides support for both SMART on FHIR V1 and V2 as described below.
SMART_ON_FHIR_V1– Support for only SMART on FHIR V1, which includesread(read/search) andwrite(create/update/delete) permissions.SMART_ON_FHIR– Support for both SMART on FHIR V1 and V2, which includescreate,read,update,delete, andsearchpermissions.AWS_AUTH– The default HealthLake authorization strategy; not affiliated with SMART on FHIR.
fineGrainedAuthorizationEnabledoptionalboolean | IResolvablefine_grained_authorization_enabledoptionaltyping.Union[bool, IResolvable]fineGrainedAuthorizationEnabledoptionalBooleanFineGrainedAuthorizationEnabledoptionalboolFineGrainedAuthorizationEnabledoptionalinterface{}#idpLambdaArnoptionalstringidp_lambda_arnoptionalstridpLambdaArnoptionalStringIdpLambdaArnoptionalstringIdpLambdaArnoptional*string#metadataoptionalstringmetadataoptionalstrmetadataoptionalStringMetadataoptionalstringMetadataoptional*string#notes
Required elements are listed based on the launch specification of the SMART application. For more information on all possible elements, see Metadata in SMART's App Launch specification.
authorization_endpoint : The URL to the OAuth2 authorization endpoint.
grant_types_supported : An array of grant types that are supported at the token endpoint. You must provide at least one grant type option. Valid options are authorization_code and client_credentials .
token_endpoint : The URL to the OAuth2 token endpoint.
capabilities : An array of strings of the SMART capabilities that the authorization server supports.
code_challenge_methods_supported : An array of strings of supported PKCE code challenge methods. You must include the S256 method in the array of PKCE code challenge methods.