Is the change to support this on the client or on the server? I've put in requests for both Jamstash and Dsub to support the new API version, but I would want to give them a heads-up if there is something on the client needed to support this. However, I wouldn't expect the client to need to know the server's backend authentication model.

Using 7200, the client doesn't give the passthrough message anymore. Instead, it can't authenticate the LDAP user at all now. The app says " Connection failure. Wrong username or password". The madsonic log says "Login failed" for user. I can successfully log into the web interface with the same user credentials.

troycarpenter wrote:Using 7200, the client doesn't give the passthrough message anymore. Instead, it can't authenticate the LDAP user at all now. The app says " Connection failure. Wrong username or password". The madsonic log says "Login failed" for user. I can successfully log into the web interface with the same user credentials.

I'm seeing this with ALL users on the mobile app, not jus LDAP. Have you tried making sure it's not just the LDAP authenticated users?

Using 7200, the client doesn't give the passthrough message anymore. Instead, it can't authenticate the LDAP user at all now. The app says " Connection failure. Wrong username or password". The madsonic log says "Login failed" for user. I can successfully log into the web interface with the same user credentials.

Bumping this. Am using 5.7.1 codebase 386. The Connection Failure. Wrong Username or password message appears when either generating an LDAP token or testing the connection. Can also see the bad login attempts in the server log.

I'm seeing this with ALL users on the mobile app, not jus LDAP. Have you tried making sure it's not just the LDAP authenticated users?

On an old stable release 6.0.7860 not using LDAP, I can get the app to test the connection and say OK but as soon as I browse for music it says wrong username or password. The login attempt is noted by the server log.