Federation API - Revision history

Tom: /* References */

2022-07-03T19:50:43Z

‎References

2022-07-03T19:50:01Z

‎References

2018-11-05T00:26:50Z

‎References

2018-11-03T18:59:08Z

‎Solution

2018-11-03T18:55:13Z

‎Solution

2018-11-03T18:54:19Z

‎Solution

2018-11-03T18:50:49Z

‎References

2018-11-03T18:49:48Z

‎Solution

2018-11-03T18:38:44Z

‎Problem

2018-11-03T18:37:54Z

‎Solution

@@ Line 46: / Line 46: @@
 [[Category: Glossary]]
 [[Category: Standard]]
-[[Category: Identifier]]
+[[Category: Federation]]

@@ Line 44: / Line 44: @@
 *[https://www.incommon.org/federation/ InCommon Federation] has been running for several years now with [[SAML 2.0]].
-[[Category:Glossary]]
+[[Category: Glossary]]
-[[Category:Standard]]
+[[Category: Standard]]

@@ Line 42: / Line 42: @@
 ==References==
 *Example of conversion from existing IDEF registry to a OpenID-like syntax. http://trustregistry.us-east-2.elasticbeanstalk.com/Registry/Display?QueryString=&reqtype=json
+*[https://www.incommon.org/federation/ InCommon Federation] has been running for several years now with [[SAML 2.0]].
 [[Category:Glossary]]
 [[Category:Standard]]

@@ Line 32: / Line 32: @@
    "dateListed": "October 31 2017 2:47pm",
    "services": [5 items],
-   "roles": null,
+   "roles": [rp iap ua],
    "counts": {3 items},
    "scores": {9 items}

@@ Line 36: / Line 36: @@
    "scores": {9 items}
+  }
+}
 </pre>

@@ Line 16: / Line 16: @@
 ==Solution==
 In order to satisfy [[User]]s in a heterogeneous environment each response needs be interpretable on its own irrespective of the federation or API version used. In the sample from the link below it can be seen that the version a federation office are the first mandatory items and that multiple results are possibly displayed (including no results at all). We expect that conversion to jwt is optional and might only occur when one specific endpoint is requested.
 ==References==

@@ Line 9: / Line 9: @@
 ==Problem==
 The [[Federation API]] need to solve the following set of [[User]] expectations.
-# The user is not familiar with the specific syntax of any federation by wishes to learn more about the members by query.
+# The user is not familiar with the specific syntax of any federation by wishes to learn more about the members by creating a query in their own language.
 # [[Framework Profile]]s will each create a different list of required and optional elements.
 # Each [[Federation Office]] will have their own update cycle with respect not only to their own elements but also the implemented version of the API.

← Older revision		Revision as of 18:37, 3 November 2018
Line 15:		Line 15:

	==Solution==		==Solution==
		+	In order to satisfy [[User]]s in a heterogeneous environment each response needs be interpretable on its own irrespective of the federation or API version used.

	==References==		==References==