Best Practice and Example Self-issued Identifier - Revision history

Tom: /* Model of the User in the Database */

2022-10-12T16:31:47Z

‎Model of the User in the Database

Tom: /* Schema used in the Example */

2021-07-15T04:41:15Z

‎Schema used in the Example

Tom: /* Implementation Guidance for Android */

2020-02-20T22:30:10Z

‎Implementation Guidance for Android

Tom: /* Implementation Guidance for UWP */

2020-01-23T01:09:24Z

‎Implementation Guidance for UWP

Tom: /* Implementation Guidance for UWP */

2020-01-20T06:33:48Z

‎Implementation Guidance for UWP

Tom: /* Implementation Guidance for UWP */

2020-01-18T19:34:58Z

‎Implementation Guidance for UWP

Tom: /* Implementation Guidance for UWP */

2020-01-18T19:34:24Z

‎Implementation Guidance for UWP

Tom: /* Implementation Guidance for UWP */

2020-01-18T19:33:49Z

‎Implementation Guidance for UWP

Tom: /* Implementation Guidance for UWP */

2020-01-18T19:32:04Z

‎Implementation Guidance for UWP

Tom: /* Implementation Guidance for Android */

2020-01-14T03:36:34Z

‎Implementation Guidance for Android

@@ Line 61: / Line 61: @@
 For more information see this page on [[User Private Information]].
 ====Model of the User in the Database====
-The goal of the data collected (as a [[User Object]]) about the individual and organizational users is to model the [[User]]s that are served by the web site with [[User Private Information]] intended for release by the users. Field names taken from other standards, like Open ID Connect, are highlighted in blue. This is a practice where the RP can determine the category tag used on each data field in advance based on the needs of the site. It may be necessary for the RP get user consent which requires that some fields are dynamically tagged based on user intent or user actions. In those cases are more complex design might be required. For example a deletion date may need to be associated with some fields.
+The goal of the data collected (as a [[User Object]]) about the individual and organizational users is to model the [[User]]s that are served by the web site with [[User Private Information]] intended for release by the users. Field names taken from other standards, like Open ID Connect, are highlighted in blue. This is a practice where the RP can determine the category tag used on each data field in advance based on the needs of the site. It may be necessary for the RP get user consent which requires that some fields are dynamically tagged based on user intent or user actions. In those cases a more complex design might be required. For example a deletion date may need to be associated with some fields.
 {|border="1" padding="2" width="799px"

@@ Line 187: / Line 187: @@
+   }
-ID Tokens MUST be signed using [[JWS]] and optionally both signed and then encrypted using [[JWS]] and [[JWE]] respectively, thereby providing authentication, integrity, non-repudiation, and optionally, confidentiality.
+ID Tokens MUST be signed using [[JWS]] and optionally both signed and then encrypted using [[JWS]] and [[JWE]] respectively, thereby providing authentication, integrity, [[Non-Repudiation]], and optionally, confidentiality.
 *Identity OPTIONAL(not included in the [[OpenID Connect]] documentation) Identity proofing indicates the type or locations of the identity proofing that was performed.
 *acr OPTIONAL. Authentication Context Class Reference. String specifying an Authentication Context Class Reference value that identifies the Authentication Context Class that the authentication performed satisfied. The value "0" indicates the End-User authentication did not meet any of the NIST SP 800-61-3 criteria.

@@ Line 266: / Line 266: @@
 ===Implementation Guidance for Android===
 *[https://docs.microsoft.com/en-us/xamarin/android/get-started/java-developers Xamarin for Java Developers].
 *[https://visualstudio.microsoft.com/vs/msft-android-emulator/ MSFT Android Emulator]
 *[https://developer.android.com/studio/ The Google Android emulator for Windows] is recommended over the one from Visual Studio by Microsoft.

@@ Line 296: / Line 296: @@
 * [https://stackoverflow.com/questions/48319459/visual-studio-2017-error-dep6200-bootstrapping-failed/48353111 DEP600 device error] is encountered when the incorrect device/emulator/local machine and platform/ARM/X86/x64 is selected in Visual Studio.
 * [https://helgeklein.com/blog/2017/01/uwp-universal-windows-app-data-storage-admins/ Universal Windows App Data Storage for Admins]
 * Exception thrown in Agent.UWP.exe: WinRT originate error - 0x80070057 : 'FormsCommandBarStyle.xaml is not a valid absolute URI.<pre>After some investigation, I discovered that if XAML is being used the app needs to be debugged in a container, which presumably VS starts automatically when launching an app the usual way from the VS IDE (e.g. using F5). To get the same result when debugging notifications, services etc., don't use the code shown at the top of this post. Instead open the Properties page for the UWP project, select the Debug pane, and then check the option "Do not launch, but debug my code when it starts". Like magic, debugging of notifications, services etc. works effortlessly. For ref., see https://docs.microsoft.com/en-us/visualstudio/debugger/start-a-debugging-session-for-a-store-app-in-visual-studio-vb-csharp-cpp-and-xaml?view=vs-2017</pre>

@@ Line 295: / Line 295: @@
 * [https://docs.microsoft.com/en-us/windows/uwp/launch-resume/handle-uri-activation Handle URI activation.]
 * [https://stackoverflow.com/questions/48319459/visual-studio-2017-error-dep6200-bootstrapping-failed/48353111 DEP600 device error] is encountered when the incorrect device/emulator/local machine and platform/ARM/X86/x64 is selected in Visual Studio.
 * Exception thrown in Agent.UWP.exe: WinRT originate error - 0x80070057 : 'FormsCommandBarStyle.xaml is not a valid absolute URI.<pre>After some investigation, I discovered that if XAML is being used the app needs to be debugged in a container, which presumably VS starts automatically when launching an app the usual way from the VS IDE (e.g. using F5). To get the same result when debugging notifications, services etc., don't use the code shown at the top of this post. Instead open the Properties page for the UWP project, select the Debug pane, and then check the option "Do not launch, but debug my code when it starts". Like magic, debugging of notifications, services etc. works effortlessly. For ref., see https://docs.microsoft.com/en-us/visualstudio/debugger/start-a-debugging-session-for-a-store-app-in-visual-studio-vb-csharp-cpp-and-xaml?view=vs-2017</pre>

@@ Line 272: / Line 272: @@
 *Set the appropriate permissions in Android Manifest - ACCESS_NETWORK_STATE INTERNET
 *[https://developers.google.com/web/tools/chrome-devtools/remote-debugging Get Started with Remote Debugging Android Devices] will help debugging your agent code that is displayed in the device browser.
-* Android Keystore system protects key material from unauthorized use. Firstly, Android Keystore mitigates unauthorized use of key material outside of the Android device by preventing extraction of the key material from application processes and from the Android device as a whole. Secondly, Android KeyStore mitigates unauthorized use of key material on the Android device by making apps specify authorized uses of their keys and then enforcing these restrictions outside of the apps' processes
+* [https://developer.android.com/training/articles/keystore Android Keystore system] protects key material from unauthorized use. Firstly, Android Keystore mitigates unauthorized use of key material outside of the Android device by preventing extraction of the key material from application processes and from the Android device as a whole. Secondly, Android KeyStore mitigates unauthorized use of key material on the Android device by making apps specify authorized uses of their keys and then enforcing these restrictions outside of the apps' processes
 ===Implementation Guidance for iOS===