fredflix 31 Posted August 6, 2020 Posted August 6, 2020 On 7/27/2020 at 10:41 AM, PenkethBoy said: i just went into swagger used the endpoint /users/new to create a new user then used the id of that user with /users/93b347e425584a8ba1b0f64b00be08f1/password end point e.g. { "Id": "93b347e425584a8ba1b0f64b00be08f1", "CurrentPw": "", "NewPw": "1234", "ResetPassword": true } you get a 204 response - which means "success no content returned" if that does not work - try it without https and your domain name The endpoint seems to work fine in swagger because it uses the swagger temporary API key. Try using an API key generated in your Emby dashboard > Advanced > API Keys You will then get a 500 response when using that API key for the /Users/{Id}/Password endpoint.
PenkethBoy 2068 Posted August 6, 2020 Posted August 6, 2020 i always authenticate as a admin user - never use the api keys via the dashboard so try with the access token returned from an admin user - once logged in
fredflix 31 Posted August 6, 2020 Posted August 6, 2020 33 minutes ago, PenkethBoy said: i always authenticate as a admin user - never use the api keys via the dashboard so try with the access token returned from an admin user - once logged in Yes it works using the user authentication method. But still, it should work as well using the API key auth method. All the other endpoints work fine with the API key auth method, no reason why this specific endpoint should be left out. Using the user auth method for development is fine even if there's an extra request to be made compared to the api key auth method, but in production, I'd rather expose an api key instead of my account password.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now