Best Practice and Example Relying Party - Revision history

Tom: /* Next steps */

2021-08-18T21:42:57Z

‎Next steps

Tom: /* Next steps */

2021-08-18T21:42:13Z

‎Next steps

Tom: /* Non-goals for this Example */

2019-11-26T01:34:09Z

‎Non-goals for this Example

Tom: /* Full Name and Status */

2019-10-10T01:40:13Z

‎Full Name and Status

Tom: /* Working Notes */

2019-02-23T20:09:25Z

‎Working Notes

Tom: /* Issues and Comments */

2019-02-23T20:06:13Z

‎Issues and Comments

Tom: /* Full Name and Status */

2019-02-23T17:49:51Z

‎Full Name and Status

Tom: /* Access to the Example */

2019-02-23T17:48:55Z

‎Access to the Example

Tom: /* Context */

2019-02-23T17:46:25Z

‎Context

Tom: /* Full Name and Status */

2019-02-23T17:45:46Z

‎Full Name and Status

@@ Line 166: / Line 166: @@
 ===Next steps===
-Set up goals and start to build examples and best practices for all of the roles in an ID ecosystem.
+Set up goals and start to build examples and best practices for all of the roles in an [[Identity Ecosystem]].
 # Now that the IDEF has established a self assessment, work on enabling the [[Identity Ecosystem]] needs enable relying parties and other entities to comply.

@@ Line 168: / Line 168: @@
 Set up goals and start to build examples and best practices for all of the roles in an ID ecosystem.
-# Now that the IDEF has established a self assessment, work on enabling the ID ecosystem needs enable relying parties and other entities to comply.
+# Now that the IDEF has established a self assessment, work on enabling the [[Identity Ecosystem]] needs enable relying parties and other entities to comply.
 # Promote a Trustmark with UX collateral, images of various sizes for web sites.
 # The Kantara web site itself should be an example of Guidelines.

@@ Line 26: / Line 26: @@
 ===Non-goals for this Example===
-This project is limited to the case of one user interacting with one Relying Party (RP) over an extended period of time using one or more Identity Providers (IdPs). The example does not consider the case where privacy enhancing technology is used to prevent linkage between different instances of use of the internet.
+This project is limited to the case of one user interacting with one Relying Party (RP) over an extended period of time using one or more Identity Providers (IdPs). The example does not consider the case where some privacy enhancing [[Technology Solution]] is used to prevent linkage between different instances of use of the internet.
 ===Design Thinking===

@@ Line 1: / Line 1: @@
 ==Full Name and Status==
-Version 2 of the Relying party example is called '''Controls''' as it can fill the function of user data controller, resource controller or just a generic [[Relying Party]]. It is based on Microsoft open source solution ASP.NET core 2.2.
+Version 2 of the Relying party example is called '''Controls''' as it can fill the function of user data controller, resource controller or just a generic [[Relying Party]]. It is based on Microsoft [[Open Source Software]] solution ASP.NET core 2.2.
 Version 1 which was built to the IDEF baseline functional requirements is now archived at [https://wiki.idesg.org/wiki/index.php/Best_Practices_and_Example_for_RP_System#Status this site.] This example is completely new, but still seeks to comply with the IDEF BFR as well as other standards from the Kantara Initiative and the OpenID foundation on interoperability, privacy and security.

← Older revision		Revision as of 20:09, 23 February 2019
Line 163:		Line 163:

	Note that the core 1.1 version is on Bitbucket. It will be retired after the new version on GitHub with core 2.2 is fully functional.		Note that the core 1.1 version is on Bitbucket. It will be retired after the new version on GitHub with core 2.2 is fully functional.
−
−	~~===Building an ASP.NET solution from scratch===~~
−
−	*From Visual Studio add new project with: C#, MVC razor pages, Change Identifier to Individual.
−	*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].
−	** 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
−	** 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 [[Two factor authentication]]. If enabled put .AddDefaultTokenProivders() in startup and add email an phone providers.

	===Next steps===		===Next steps===

@@ Line 224: / Line 224: @@
 ===Issues and Comments===
-*Any comments, suggestions or issues with the best practices or code can be tracked at [https://bitbucket.org/tomcjones/idesg/issues this site]. You must have a sign in method for bitbucket. (This will be moved to GitHub soon.)
+*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]]

← Older revision		Revision as of 17:49, 23 February 2019
Line 7:		Line 7:

	For a less technical document that shows how the various parties hold [[User Information]] in a [[User Object]] see the [[Identity Model Overview]].		For a less technical document that shows how the various parties hold [[User Information]] in a [[User Object]] see the [[Identity Model Overview]].
		+
		+	This is still a work in progress. Do not expect full functional code at this time.

	==Context==		==Context==

@@ Line 32: / Line 32: @@
 ===Access to the Example===
-Currently a working draft of the Relying Party example web site is available here TK
+Currently a working draft of the Relying Party example web site is available [https://controls.azurewebsites.net/ here].
 ===Identifier used in Best Practices===

@@ Line 9: / Line 9: @@
 ==Context==
-This example was originally created in Microsoft ASP.NET core version 1.1. It is currently being revised to run on ASP.NET core version 2.2 so there are likely some parts that are not fully converted.
+This example was originally created in Microsoft ASP.NET core version 1.1. It is currently being revised to run on ASP.NET core version 2.2 so there are likely some parts of this wiki page that are not fully converted.
 ===Goals of the Best Practices and Example===
 In furtherance of the objective of an ecosystem of trusted identities in cyberspace, it is incumbent on the various bodies working on the [[IDEF]] to produce guidelines that can help designers and developers to create web sites that support the ecosystem. There is no better test of the existing guidelines that to create a web site that meets those goals. This example gives the UX participants the actual experience of applying their guidelines as well as providing an example of that effort for anyone designing or developing a compliant web site.
@@ Line 28: / Line 28: @@
 ===Design Thinking===
 Given the goals above, [https://en.wikipedia.org/wiki/Design_thinking design thinking] is needed to produce a solution in the form of patterns which meets the user's desires and intent. For example in the need to capture the user's acceptance of the privacy policy and the terms of use, a design pattern could just let the user read and accept the site's stated policies. But what the user wants is control on how their private information is used. The solution below tries to address both the RP site goals and the user desires in a way that allows users to see their past expressed intent and change it as befits their current intent. This is in keeping with the [[Usable Best Practice A]] of the IDEF requirements.
 ==Solution==
 ===Access to the Example===

@@ Line 4: / Line 4: @@
 Version 1 which was built to the IDEF baseline functional requirements is now archived at [https://wiki.idesg.org/wiki/index.php/Best_Practices_and_Example_for_RP_System#Status this site.] This example is completely new, but still seeks to comply with the IDEF BFR as well as other standards from the Kantara Initiative and the OpenID foundation on interoperability, privacy and security.
-This page is designed to assist designers and developers of relying party (RP) web sites, meaning those [[Web Site]]s that depend on other [[Identifier or Attribute Provider]]s. Technical terms are used to convey the information that they will need to perform their task that may not be familiar to the casual reader.
+This page is designed to assist designers and developers of relying party (RP) web sites, meaning those [[Web Site]]s that rely upon other [[Identifier or Attribute Provider]]s. Technical terms are used to convey the information that they will need to perform their task that may not be familiar to the casual reader.
 For a less technical document that shows how the various parties hold [[User Information]] in a [[User Object]] see the [[Identity Model Overview]].