Custom BackOffice Authentication Provider for Version 9
I am looking to upgrade our current 8.16.0 instance to version 9. We are currently authenticating to the BackOffice using a custom OWIN provider I wrote to authenticate against Active Directory using LDAP. I did this with a custom OwinStartup configured in Web.Config that overrides the default IBackOfficeUserPasswordChecker. I haven't seen any examples of how to do this in version 9 yet. Any examples or details that you can provide would be greatly appreciated.
No one ever responded to this so we had to move to a different type of authentication. I was really hoping to keep using LDAP but I just didn't know how to get it working. I ended up using OpenId to integrate with our authentication.
No, that is what I ended up using, but not what I was looking for. I was looking for how to override the built-in login like we used to be able to do so I could use the built-in login form but authenticate that username and password against LDAP. You use to be able to override the built-in IBackOfficeUserPasswordChecker. I've not found anything about how to do that in version 9. I ended up using an OpenId provider.
Hi Brad, I need the same as you.
I managed to use AD authentication on Umbraco 8, using LDAP, but how can I do it in Umbraco 9? Did you find any solution?
No, I was never able to get any information about creating a custom login provider like we could do in previous versions. Instead, I went with an OpenId provider as we use Okta for authentication at our university.
Is there a solution in version 9 or 10 to work with LDAP like we did in 8?
Use IBackOfficeUserPasswordChecker but disable Umbraco's built-in check in the umbracousers table.
The postLogin service now returns me ERROR 400
Custom BackOffice Authentication Provider for Version 9
I am looking to upgrade our current 8.16.0 instance to version 9. We are currently authenticating to the BackOffice using a custom OWIN provider I wrote to authenticate against Active Directory using LDAP. I did this with a custom OwinStartup configured in Web.Config that overrides the default IBackOfficeUserPasswordChecker. I haven't seen any examples of how to do this in version 9 yet. Any examples or details that you can provide would be greatly appreciated.
Hi Brad,
Did you find a solution? I'm looking for something similar.
Br Lasse
No one ever responded to this so we had to move to a different type of authentication. I was really hoping to keep using LDAP but I just didn't know how to get it working. I ended up using OpenId to integrate with our authentication.
Hi All,
I think here it is External Login Providers ;)
Regards
Dhanesh Kumar MJ
No, that is what I ended up using, but not what I was looking for. I was looking for how to override the built-in login like we used to be able to do so I could use the built-in login form but authenticate that username and password against LDAP. You use to be able to override the built-in IBackOfficeUserPasswordChecker. I've not found anything about how to do that in version 9. I ended up using an OpenId provider.
Hello Brad and Dhanesh,
Thank you 😊👍
I ended up using Azure AD...
Br Lasse
Hi Brad, I need the same as you. I managed to use AD authentication on Umbraco 8, using LDAP, but how can I do it in Umbraco 9? Did you find any solution?
Hi Pablo,
Did you ever find a solution to authenticate with Azure AD?
I am creating an internal intranet where I want to authenticate the users (Umrbaco Members) against Azure AD.
Mark
No, I was never able to get any information about creating a custom login provider like we could do in previous versions. Instead, I went with an OpenId provider as we use Okta for authentication at our university.
Is there a solution in version 9 or 10 to work with LDAP like we did in 8? Use IBackOfficeUserPasswordChecker but disable Umbraco's built-in check in the umbracousers table. The postLogin service now returns me ERROR 400
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.