Compliant Implementation of RP on ASP.NET - Revision history

Tom: /* Issues and Comments */

2021-06-16T18:21:18Z

‎Issues and Comments

2019-03-21T22:07:26Z

‎References and Coordination

2019-03-17T21:54:24Z

‎Access to the Example

2019-03-17T21:54:01Z

‎References and Coordination

2019-03-17T21:53:35Z

‎References and Coordination

2019-03-06T21:05:30Z

‎Issues and Comments

2019-03-04T01:29:19Z

‎Building an ASP.NET solution from scratch

2019-03-04T01:26:42Z

‎Building an ASP.NET solution from scratch

2019-02-26T01:46:19Z

‎Building an ASP.NET solution from scratch

2019-02-26T01:44:10Z

‎References and Coordination

@@ Line 82: / Line 82: @@
 *The Microsoft web site has a description of the [https://docs.microsoft.com/en-us/aspnet/core/api/microsoft.aspnet.identity.corecompat Namespaces in ASP.NET Core] that  can be used as an alternate identity schema. It was the precursor for the schema used here.
 *[https://docs.microsoft.com/en-us/visualstudio/debugger/remote-debugging-azure?view=vs-2017 this site] describes how to debug this app if running an Azure. Other scenarios are available near where that link goes.
+*[https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/tree/dev/src source code for Microsoft IdentityModel OpenIDConnect]
 ===Issues and Comments===

← Older revision		Revision as of 21:54, 17 March 2019
Line 17:		Line 17:

	Currently a working draft of the Relying Party example web site is available [https://controls.azurewebsites.net/ here].		Currently a working draft of the Relying Party example web site is available [https://controls.azurewebsites.net/ here].
−
−
−	~~[[File:Social-combo.png]]~~

	==Working Notes==		==Working Notes==

@@ Line 84: / Line 84: @@
 *The page at [[Best Practice and Example Relying Party]] gives a more architectural and design approach to creating a compliant RP site.
 *The Microsoft web site has a description of the [https://docs.microsoft.com/en-us/aspnet/core/api/microsoft.aspnet.identity.corecompat Namespaces in ASP.NET Core] that  can be used as an alternate identity schema. It was the precursor for the schema used here.
-*[https://docs.microsoft.com/en-us/visualstudio/debugger/remote-debugging-azure?view=vs-2017 this site] describes how to debug this site if running an Azure. Other scenarios are available near where that link goes.
+*[https://docs.microsoft.com/en-us/visualstudio/debugger/remote-debugging-azure?view=vs-2017 this site] describes how to debug this app if running an Azure. Other scenarios are available near where that link goes.
 ===Issues and Comments===

@@ Line 84: / Line 84: @@
 *The page at [[Best Practice and Example Relying Party]] gives a more architectural and design approach to creating a compliant RP site.
 *The Microsoft web site has a description of the [https://docs.microsoft.com/en-us/aspnet/core/api/microsoft.aspnet.identity.corecompat Namespaces in ASP.NET Core] that  can be used as an alternate identity schema. It was the precursor for the schema used here.
 ===Issues and Comments===

@@ Line 89: / Line 89: @@
 *Any comments, suggestions or issues with the best practices or code can be tracked at [https://github.com/TomCJones/Controls/issues this site]. You must have a sign in method for GitHub.
 *General comments about this web page can be made on the "Discussion" tab at the top of the page. You must be a registered member of this site to make comments here.
 [[Category:User Experience]]
 [[Category:Best Practice]]

@@ Line 32: / Line 32: @@
 *Take control of the user information by overriding the IdentityUser with a local name, here we use the name UserObject to align with terminology in this wiki.
 **It is common to include UserGroup as well as UserObject in the definition if the admin or other types of user will be included in the same database.
-*[https://docs.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-2.2&tabs=visual-studio Scaffold Identity in ASP.NET Core projects].
+*[https://docs.microsoft.com/en-us/aspnet/core/security/authentication/scaffold-identity?view=aspnetcore-2.2&tabs=visual-studio Scaffold Identity in ASP.NET Core 2 projects].
 ** for this example choose the instructions labled "Scaffold identity into a Razor project without existing authorization"
 ** In the project right-click select add -> scaffold -> Identity and override all files, type in layout cshtml name, DB name and UserObject

@@ Line 37: / Line 37: @@
 ** If you have your own definition of the user before scaffolding, you might wind up with two definitions; delete one.
 ** Make a choice about enabling [[Multi-factor Authentication|Two factor authentication]]. If enabled put .AddDefaultTokenProivders() in startup and add email and/or phone providers.
 ===Next steps===

@@ Line 81: / Line 81: @@
 ==References and Coordination==
-*The page at [[Compliant Implementation of RP on ASP.NET]] gives a more technical description of the process for building a compliant Relying Party web site from scratch.
+*The page at [[Best Practice and Example Relying Party]] gives a more architectural and design approach to creating a compliant RP site.
 *The Microsoft web site has a description of the [https://docs.microsoft.com/en-us/aspnet/core/api/microsoft.aspnet.identity.corecompat Namespaces in ASP.NET Core] that  can be used as an alternate identity schema. It was the precursor for the schema used here.