Class UserNameIdentityResolver
Resolver for SuperOffice "native" user name + password authentication
Implements
Inherited Members
Namespace: SuperOffice.Security.Principal
Assembly: SoDataBase.dll
Syntax
[SoIdentityResolver("UserNameIdentityResolver", 2000)]
public sealed class UserNameIdentityResolver : AssociateResolver, ISoIdentityResolver
Remarks
SuperOffice passwords are stored in the credentials table, with the CRM5/PASSWORD identifier. The secret contains a db-tag + associate_id salted hash of the password, non-reversible. Just knowing the hash will not get in either...
Constructors
UserNameIdentityResolver()
Resolver for SuperOffice "native" user name + password authentication
Declaration
public UserNameIdentityResolver()
Remarks
SuperOffice passwords are stored in the credentials table, with the CRM5/PASSWORD identifier. The secret contains a db-tag + associate_id salted hash of the password, non-reversible. Just knowing the hash will not get in either...
Fields
DbCredentialType
How is this kind of credential identified in the database
Declaration
public const string DbCredentialType = "CRM5/PASSWORD"
Field Value
Type | Description |
---|---|
string |
Remarks
SuperOffice passwords are stored in the credentials table, with the CRM5/PASSWORD identifier. The secret contains a db-tag + associate_id salted hash of the password, non-reversible. Just knowing the hash will not get in either...
Methods
ResolveIdentityAsync(IEnumerable<ClaimsIdentity>, SoConnection)
Resolver for SuperOffice "native" user name + password authentication
Declaration
public override Task<(ClaimsIdentity claims, string reason)> ResolveIdentityAsync(IEnumerable<ClaimsIdentity> identities, SoConnection dbConnection)
Parameters
Type | Name | Description |
---|---|---|
IEnumerable<ClaimsIdentity> | identities | |
SoConnection | dbConnection |
Returns
Type | Description |
---|---|
Task<(ClaimsIdentity claims, string reason)> |
Overrides
Remarks
SuperOffice passwords are stored in the credentials table, with the CRM5/PASSWORD identifier. The secret contains a db-tag + associate_id salted hash of the password, non-reversible. Just knowing the hash will not get in either...