Jump to: navigation, search

Difference between revisions of "SYSCLS EXTERNALENTITY"


(See also)
(Usage)
 
(2 intermediate revisions by the same user not shown)
Line 20: Line 20:
  
 
The purpose of this classification is to transport a previously acquired auth token from the client to the server.  
 
The purpose of this classification is to transport a previously acquired auth token from the client to the server.  
Add this classification to all meta classes you have defined an [[SYSCLS_EXTERNALAUTHCONFIG|External Auth Configuration]] entry for.
+
Add this classification to all scopes of meta classes you have defined an [[SYSCLS_EXTERNALAUTHCONFIG|External Auth Configuration]] entry for.
Since this is an autonomous classification, you don't need to do anything else (like adapting a scope).
+
Since this is an autonomous classification, the MP_EXTAUTHTOKEN meta property should be added to the scope automatically during runtime.
 +
Also, add this classification to the meta class itself, since the Content web service only caches the external auth token if this classification is found on the meta class.
 +
 
 +
[[Category:Classifications|E]]
  
 
== See also ==
 
== See also ==

Latest revision as of 13:39, 22 March 2022

IC CLASSIFICATION.gif External Entity Classification (SSO)
Name SYSCLS_EXTERNALENTITY
Inheritance -
Namespace System.Classification.SSO
ID {4b9fcdbc-3281-4f79-a20a-260ef8287c1d}
Purpose Classify entities represented in external systems, requiring authorization for interaction
Version 3.6.1+

MetaProperties

Name Data type Comment
MP_EXTAUTHTOKEN String An SSO authentication/authorization token used for interaction with external systems regarding this object

Usage

The purpose of this classification is to transport a previously acquired auth token from the client to the server. Add this classification to all scopes of meta classes you have defined an External Auth Configuration entry for. Since this is an autonomous classification, the MP_EXTAUTHTOKEN meta property should be added to the scope automatically during runtime. Also, add this classification to the meta class itself, since the Content web service only caches the external auth token if this classification is found on the meta class.

See also