Customer-specific SAML OAuth SSO Configurations - Revision history

WikiSysop at 09:43, 5 September 2022

2022-09-05T09:43:34Z

WikiSysop at 09:42, 5 September 2022

2022-09-05T09:42:37Z

WikiSysop at 09:41, 5 September 2022

2022-09-05T09:41:27Z

WikiSysop at 09:40, 5 September 2022

2022-09-05T09:40:46Z

WikiSysop at 09:40, 5 September 2022

2022-09-05T09:40:19Z

WikiSysop: Created page with " This is an enhancement. Previously, saml2federation.config or AzureADB2c.config were stored in web.config. Any changes to these configurations resulted into app domain loadin..."

2022-09-05T09:36:34Z

Created page with " This is an enhancement. Previously, saml2federation.config or AzureADB2c.config were stored in web.config. Any changes to these configurations resulted into app domain loadin..."

New page

This is an enhancement. Previously, saml2federation.config or AzureADB2c.config were stored in web.config. Any changes to these configurations resulted into app domain loading/unloading and 1st call slowness. Additionally, any mistake in configuration led to entire POD failure. To overcome this problem, service providers and their respective metadata from saml2Federation.config will be extracted and saved in separate config files. These new config files for the tenant will be stored within "SSO" folder, so that all config files/hook configs reside in one folder. It will be done for Multi-Tenant (MT) and Single Tenant (ST) environments. Single file for both OAuth and Saml2 configuration will be created and maintained. OAuth section will have default OAuth providers and SAML section will have specific service provider configuration. 
<div class="note-box">Note - DevOps BD will not run on AWS and AzureGOV environments. A standard manual process needs to be followed for these environments.</div>
= For SAML2 configuration   =

*DevOps team will create PowerShell script in BD (New Infra and Upgrade) to   separate service providers and their respective metadata from saml2Federation.config and save them in different config files. These new config files will be stored within "SSO" folder, so that all config files/hook configs for that tenant reside in one folder. It will be done for both Multi-Tenant (MT) and Single Tenant (ST) environments.  
*Single file will be created and maintained for both OAuth and Saml2 configurations. OAuth section will have default OAuth providers and SAML section will have specific service provider configuration. 
*The naming convention of the file would be the service provider’s “<<TenantName>>.config”. 
*Read the newly created config files in the code to get the SSO configuration. 
*Take backup of saml2Federation.config and AzureADB2C.config files 
*Delete saml2Federation.config and AzureADB2C.config files. 
*Delete the following sections from web.config file 

          <saml2Federation configSource="saml2Federation.config"></saml2Federation> and   <oauth configSource="AzureAdB2C.config"></oauth>   
<div class="note-box">Note: The fallback mechanism will work only if there is an error in the BD or the BD has not run at all. </div>
= OAUTH  =

*
DevOps team will create a PowerShell script in BD (New Infra and Upgrade) to separate OAuth Providers from AzureAdB2C.config and save them in different config files. These new config files will be stored in “SSO” folder, so that all config files/hook configs for that tenant resides in one folder. It will be done for both Multi-Tenant (MT) and Single Tenant (ST) environments.  

*
Single file will be created and maintained for both OAuth and Saml2 configurations. OAuth section will have default OAuth providers and SAML section will have specific service provider configuration 

*
The naming convention of the file would be tenant name “<<TenantName>>.config”. This file will have all the OAuth providers entry based on the OAuthProvider key value in tenant specific json file. 

*
Read the newly created config files in the code to get the SSO configuration. 

*
Take backup of AzureAdB2C.config and Saml2Federation.config files  

*
Delete file AzureAdB2C.config and Saml2Federation.config files  

*
Delete following sections from web.config file 

          <saml2Federation configSource="saml2Federation.config"></saml2Federatio> and   <oauth configSource="AzureAdB2C.config"></oauth>   

 
<div class="note-box" paraeid="{66f0010c-42e7-4a47-95cb-dc040fdaf001}{154}" paraid="1450662539">Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all. </div>
 

= Other Authentication Type  =

*
DevOps team will create a PowerShell script in BD (New Infra and Upgrade) to create default file containing default OAuth Providers from AzureAdB2C.config and save them in different config files. These new config files will be stored in tenant specific folder inside "SSO" folder, so that all config files/hook configs for that tenant resides in one folder. It will be done for both Multi-Tenant (MT) and Single Tenant (ST) environments.  

*
The naming convention of the file would be tenant name “<<TenantName>>.config”. This file will have only default OAuth providers entries necessary and saml service provider in the section will be left blank 

*
Read the newly created config files in the code to get the SSO configuration. 

*
Take backup of AzureAdB2C.config and saml2Federation.config files 

*
Delete AzureAdB2C.config and saml2Federation.config files 

*
Delete the following sections from web.config file 

          <oauth configSource="AzureAdB2C.config"></oauth> and <saml2Federation configSource="saml2Federation.config"></saml2Federation>  

 
<div class="note-box" paraeid="{7acf3800-718e-43fc-88af-cff864f4f2ff}{6}" paraid="166386619">Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all. </div>

@@ Line 14: / Line 14: @@
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <saml2Federation configSource="saml2Federation.config"></saml2Federation> and   <oauth configSource="AzureAdB2C.config"></oauth>  &nbsp;
 <div class="note-box">Note: The fallback mechanism will work only if there is an error in the BD or the BD has not run at all.&nbsp;</div>
 = OAUTH&nbsp; =
@@ Line 29: / Line 27: @@
 &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; <saml2Federation configSource="saml2Federation.config"></saml2Federatio> and   <oauth configSource="AzureAdB2C.config"></oauth>  &nbsp;
-&nbsp;
+Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all.&nbsp;
-<div class="note-box">Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all.&nbsp;</div>
 &nbsp;
 = Other Authentication Type&nbsp; =

@@ Line 2: / Line 2: @@
 This is an enhancement. Previously, saml2federation.config or AzureADB2c.config were stored in web.config. Any changes to these configurations resulted into app domain loading/unloading and 1st call slowness. Additionally, any mistake in configuration led to entire POD failure. To overcome this problem, service providers and their respective metadata from saml2Federation.config will be extracted and saved in separate config files. These new config files for the tenant will be stored within "SSO" folder, so that all config files/hook configs reside in one folder. It will be done for Multi-Tenant (MT) and Single Tenant (ST) environments. Single file for both OAuth and Saml2 configuration will be created and maintained. OAuth section will have default OAuth providers and SAML section will have specific service provider configuration.&nbsp;
 <div class="note-box">Note -&nbsp;DevOps BD will not run on AWS and AzureGOV environments. A standard manual process needs to be followed for these environments.</div>
 = For SAML2 configuration &nbsp; =

← Older revision		Revision as of 09:40, 5 September 2022
Line 16:		Line 16:
	= OAUTH  =		= OAUTH  =

−	*	+	*DevOps team will create a PowerShell script in BD (New Infra and Upgrade) to separate OAuth Providers from AzureAdB2C.config and save them in different config files. These new config files will be stored in “SSO” folder, so that all config files/hook configs for that tenant resides in one folder. It will be done for both Multi-Tenant (MT) and Single Tenant (ST) environments.
−	DevOps team will create a PowerShell script in BD (New Infra and Upgrade) to separate OAuth Providers from AzureAdB2C.config and save them in different config files. These new config files will be stored in “SSO” folder, so that all config files/hook configs for that tenant resides in one folder. It will be done for both Multi-Tenant (MT) and Single Tenant (ST) environments.	+	*Single file will be created and maintained for both OAuth and Saml2 configurations. OAuth section will have default OAuth providers and SAML section will have specific service provider configuration
−		+	*The naming convention of the file would be tenant name “<<TenantName>>.config”. This file will have all the OAuth providers entry based on the OAuthProvider key value in tenant specific json file.
−	*	+
−	Single file will be created and maintained for both OAuth and Saml2 configurations. OAuth section will have default OAuth providers and SAML section will have specific service provider configuration	+
−		+
−	*	+
−	The naming convention of the file would be tenant name “<<TenantName>>.config”. This file will have all the OAuth providers entry based on the OAuthProvider key value in tenant specific json file.~~ ~~	+
−		+
−		+
−	*	+
−	~~Read the newly created config files in the code to get the SSO configuration. ~~	+
−		+
−	*	+
−	~~Take backup of AzureAdB2C.config and Saml2Federation.config files  ~~	+
−		+
−	*	+
−	~~Delete file AzureAdB2C.config and Saml2Federation.config files  ~~	+
−		+
−	*	+
−	~~Delete following sections from web.config file~~	+

		+	*Read the newly created config files in the code to get the SSO configuration.
		+	*Take backup of AzureAdB2C.config and Saml2Federation.config files
		+	*Delete file AzureAdB2C.config and Saml2Federation.config files
		+	*Delete following sections from web.config file

	<saml2Federation configSource="saml2Federation.config"></saml2Federatio> and   <oauth configSource="AzureAdB2C.config"></oauth>		<saml2Federation configSource="saml2Federation.config"></saml2Federatio> and   <oauth configSource="AzureAdB2C.config"></oauth>


−	<div class="note-box~~" paraeid="{66f0010c-42e7-4a47-95cb-dc040fdaf001}{154}" paraid="1450662539~~">Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all. </div>	+	<div class="note-box">Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all. </div>


	= Other Authentication Type  =		= Other Authentication Type  =

−	*	+	*DevOps team will create a PowerShell script in BD (New Infra and Upgrade) to create default file containing default OAuth Providers from AzureAdB2C.config and save them in different config files. These new config files will be stored in tenant specific folder inside "SSO" folder, so that all config files/hook configs for that tenant resides in one folder. It will be done for both Multi-Tenant (MT) and Single Tenant (ST) environments.
−	DevOps team will create a PowerShell script in BD (New Infra and Upgrade) to create default file containing default OAuth Providers from AzureAdB2C.config and save them in different config files. These new config files will be stored in tenant specific folder inside "SSO" folder, so that all config files/hook configs for that tenant resides in one folder. It will be done for both Multi-Tenant (MT) and Single Tenant (ST) environments.	+	*The naming convention of the file would be tenant name “<<TenantName>>.config”. This file will have only default OAuth providers entries necessary and saml service provider in the section will be left blank
−		+	*Read the newly created config files in the code to get the SSO configuration.
−	*	+
−	The naming convention of the file would be tenant name “<<TenantName>>.config”. This file will have only default OAuth providers entries necessary and saml service provider in the section will be left blank	+
−		+
−	*	+
−	Read the newly created config files in the code to get the SSO configuration.~~ ~~	+
−		+
−		+
−	*	+
−	~~Take backup of AzureAdB2C.config and saml2Federation.config files ~~	+
−		+
−	*	+
−	~~Delete AzureAdB2C.config and saml2Federation.config files ~~	+
−		+
−	*	+
−	~~Delete the following sections from web.config file~~	+

		+	*Take backup of AzureAdB2C.config and saml2Federation.config files
		+	*Delete AzureAdB2C.config and saml2Federation.config files
		+	*Delete the following sections from web.config file

	<oauth configSource="AzureAdB2C.config"></oauth> and <saml2Federation configSource="saml2Federation.config"></saml2Federation>		<oauth configSource="AzureAdB2C.config"></oauth> and <saml2Federation configSource="saml2Federation.config"></saml2Federation>


−	<div class="note-box~~" paraeid="{7acf3800-718e-43fc-88af-cff864f4f2ff}{6}" paraid="166386619~~">Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all. </div>	+	<div class="note-box">Note: The fallback mechanism will work only if there is an error in the tool or the tool has not run at all. </div>