I have back office authentication working with active directory but Courier says it cannot authenticate any user between locations. We've tried both using "user" and hard coding a login and password in the courier.config file.
We're using Umbraco 6.2 and the latest release version of Courier.
Is it possible to make Courier work with LDAP or is there a way to have Courier use the default Umbraco back office provider instead of the custom one?
In general, however you have your users membership provider configured is what Courier will use. Courier does a very simple .IsAuthenticated() call using the Umbraco core methods taking only user name and password as arguments. So it compares the literal user name and the password (clear | hashed) that your provide to Courier with that returned from your provider. In that sense, make sure your provider is using same hashing approach on your source and target environments and if you are salting the password, that the salt is the same both places. Or whatever other approach you need to use to ensure the string comparison will be comparing equal strings.
Courier and LDAP
I have back office authentication working with active directory but Courier says it cannot authenticate any user between locations. We've tried both using "user" and hard coding a login and password in the courier.config file.
We're using Umbraco 6.2 and the latest release version of Courier.
Is it possible to make Courier work with LDAP or is there a way to have Courier use the default Umbraco back office provider instead of the custom one?
@Richard
In general, however you have your users membership provider configured is what Courier will use. Courier does a very simple .IsAuthenticated() call using the Umbraco core methods taking only user name and password as arguments. So it compares the literal user name and the password (clear | hashed) that your provide to Courier with that returned from your provider. In that sense, make sure your provider is using same hashing approach on your source and target environments and if you are salting the password, that the salt is the same both places. Or whatever other approach you need to use to ensure the string comparison will be comparing equal strings.
By default Courier uses hashed password encoding:
<url>http://umbraco-prod.mydomain.org</url>;
<login>courier_user</login>
<password>1234</password>
<passwordEncoding>Hashed</passwordEncoding>
is working on a reply...