This article will provide you with the global terminology we use when we are talking "Fischer-ese". This way, you know what we are talking about when we discuss your solution or answer any of your questions. We think this is a great starting point for you to learn more about how we do Identity at Fischer.
|An identity is the representation of a user within Fischer. An identity is a combination of attributes that creates an entity within Fischer. Identities can have the same attributes or different attributes as well as the corresponding values associated with the attributes can the different. A Fischer Identity is stored in a combination of tables which will be discussed in detail in our "How a person becomes a Fischer Identity" course.|
|An account to Fischer is an actual Connected System account. It is not the Identity itself. When referring to accounts, you should consider the context. You should never refer to a user's Identity as an account. Always be sure to distinguish an account from the actual Identity. Accounts are associated with the Fischer Identity. The Identity is not an account.|
|The "Resource" is the fundamental building block for your entire Fischer solution. A Resource is a component of the IGA Solution that can be acted upon by multiple features. A resource can be an account or an entitlement. A resource is something that be provisioned to Identities and their associated accounts.|
|An attribute is the fundamental component of defining an identity. Each identity will have a set of attributed stored within Fischer's Identity Registry|
|The "Identity Registry"|
|The Identity Registry is the location within Fischer where all attributes associated with a particular identity are stored and referenced across various features of the product. The Registry also contains account and entitlement associations to the Fischer Identity providing IGA Administrators and relevant users with a transparent view of which accounts and entitlements are associated with an Identity.|
|"A Connected System"|
|A connected system is an integration with a customer's third party target systems. For example, Google Apps, Office 365, etc. Fischer also refers to connected systems as "connectors". A connected system can be a source of data for the Fischer solution to process or it can be a target system Fischer is provisioning to.|
|This term is a generic reference to Fischer's front end interfaces. The interfaces involved are the Kiosk, PIN Password Reset, Identity Claim, Forgot UserID and the Self-Service Identity Portal.|
Please sign in to leave a comment.