- Tue May 16, 2017 2:58 pm
#18268
I followed the instructions available here https://www.aspnetboilerplate.com/Pages ... entication to configure the LDAP authentication and it's working as expected when invoked via:
TryAuthenticateAsync is invoked as expected and it works smoothly, but I'd need to use 2 distinct authentication methods:
Is there any way to combine the default authentication mechanism (=without LDAP/External source) with LDAP, based on some conditions?
I mean, is there any way to "chain" different authentication approaches as fallbacks ?
As an alternative, is it possible to invoke the "local" authentication from inside TryAuthenticateAsync in case usernameOrEmailAddress is not a valid username/e-mail?
Code: Select all
private async Task<AbpLoginResult<Tenant, User>> GetLoginResultAsync(string usernameOrEmailAddress, string password, string tenancyName)
{
var loginResult = await _logInManager.LoginAsync(usernameOrEmailAddress, password, tenancyName);
switch (loginResult.Result)
{
case AbpLoginResultType.Success:
return loginResult;
default:
throw CreateExceptionForFailedLoginAttempt(loginResult.Result, usernameOrEmailAddress, tenancyName);
}
}
TryAuthenticateAsync is invoked as expected and it works smoothly, but I'd need to use 2 distinct authentication methods:
- * LdapAuthenticationSource --> TryAuthenticateAsync if userNameOrEmailAddress is an e-mail address OR if it's in the format domain\username
* The local data (e.g. accounts available in dbo.AbpUsers) otherwise
Is there any way to combine the default authentication mechanism (=without LDAP/External source) with LDAP, based on some conditions?
I mean, is there any way to "chain" different authentication approaches as fallbacks ?
As an alternative, is it possible to invoke the "local" authentication from inside TryAuthenticateAsync in case usernameOrEmailAddress is not a valid username/e-mail?