Support Photoprism app passwords

[modem7]

Description

Latest update included app passwords, and it seems that this version of the widget does not parse this password correctly.

homepage version

0.8.12

Installation method

Docker

Configuration

## Homepage
      - homepage.name=Photoprism
      - homepage.group=Tools
      - homepage.icon=photoprism
      - homepage.href=https://photoprism.$DOMAINNAME
      - homepage.widget.type=photoprism
      - homepage.widget.url=http://photoprism:2342
      - homepage.widget.username=$PHOTOPRISM_ADMIN_USER
      - homepage.widget.password=$PHOTOPRISM_APP_PASSWORD

Container Logs

[2024-04-22T23:27:45.314Z] error: <photoprismProxyHandler> HTTP 401 getting data from PhotoPrism. Data: {"error":"Invalid credentials"}

Browser Logs

API Error: HTTP Error 401
URL: http://photoprism:2342/api/v1/session
Response Data:
{"error":"Invalid credentials"}

Troubleshooting

1. Create new app password in "apps and devices" with "Metrics" persmissions in Photoprism
2. Replace admin password with app password in Docker
3. Error occurs

[glime-ai[bot]]

Thanks for posting a discussion about homepage here on GitHub. Homepage now uses a fancy new AI tool thanks to our friends at Glime, so the answer below is the AI bot's attempt to answer your question. If you feel it's sufficient you can mark the answer and close this post, otherwise feel free to leave it open of course!

Thanks for using Homepage! ❤️

---

Based on the information provided, it seems that the issue is related to authentication with the PhotoPrism service using the app password. Since you are receiving an HTTP 401 error, this indicates that the credentials are not being accepted by PhotoPrism.

Here are some steps you can take to troubleshoot this issue:

1. Verify the App Password: Ensure that the app password you have created in PhotoPrism's "apps and devices" section is correct and has the necessary permissions.

2. Check the Environment Variables: Make sure that the environment variables $PHOTOPRISM_ADMIN_USER and $PHOTOPRISM_APP_PASSWORD are correctly set in your Docker configuration and that they are being passed correctly to the homepage widget.

3. Review the Widget Configuration: Double-check the widget configuration in your yaml file to ensure that there are no typos or formatting issues. The configuration should match the allowed fields and structure as per the PhotoPrism widget documentation.

4. Avoid Special Characters: If your app password contains special characters, they might need to be URL-encoded, or you might want to try a password without special characters to see if that resolves the issue.

5. Check PhotoPrism Logs: Look into the logs of the PhotoPrism service to see if there are any additional details about the failed authentication attempts.

6. Ensure No Trailing Slash: As per the troubleshooting documentation, ensure that the URL in the widget configuration does not end with a trailing slash, as this can cause errors.

7. Test the API Manually: You can try to manually test the PhotoPrism API using a tool like curl to see if you can authenticate successfully with the app password. This can help determine if the issue is with the homepage widget or with the PhotoPrism service itself.

If after following these steps the issue persists, you may want to reach out to the PhotoPrism support or community for further assistance, or check if there are any known issues with app passwords in the version of PhotoPrism you are using.

Please let me know if you need further assistance or if there are any specific details you would like to clarify.

This comment was generated by Glime.

[shamoon]

So this is just a breaking change for their api? why...

[shamoon]

Or are you saying the widget doesnt support app passwords, because thats more like an 'enhancement'

[modem7]

I'd say it's both. Because of the change to the API (assumption, but quite likely), a fix is required to allow it to work with their new app passwords.

As to the why's... I stopped asking that question long ago for things like this. I only have so much hair left.

[shamoon]

Actually I think it is the latter. I tested with Build 240420-ef5f14bc4 and current admin / password is working fine.

This can serve as a feature request to support app passwords.

[joeybaumgartner]

@shamoon I've got a fix to add app passwords, should I submit a PR?

[modem7]

I'd say it'd make sense to raise a PR for review if you have the fix.

[joeybaumgartner]

I've added this functionality in a branch on my side . It's a pretty simple change, but uses the property authToken instead of password to communicate what authentication method should use.

[joeybaumgartner]

PR was denied due to not referencing an up-voted feature request; something that I completely missed when submitting. @shamoon , if I re-submit and reference this issue (completely keeping in mind that it has fewer up-votes than a lot of others), would thtat be alright, or should i hold off until a particular threshhold is met?

[shamoon]

[joeybaumgartner]

@modem7 I have a fix on my side, but the PRs cannot be evaluated until there's at least 10 upvotes for a feature enhancement. I'll keep tabs on this on my side, but for the time being, this will have to wait.

[modem7]

@modem7 I have a fix on my side, but the PRs cannot be evaluated until there's at least 10 upvotes for a feature enhancement. I'll keep tabs on this on my side, but for the time being, this will have to wait.

Heya,

Thank you very much!

I'll review the PR, and in the meantime create a custom image with it.

Sincerely appreciate it!

[modem7]

@modem7 I have a fix on my side, but the PRs cannot be evaluated until there's at least 10 upvotes for a feature enhancement. I'll keep tabs on this on my side, but for the time being, this will have to wait.

Woop! 10 upvotes!

[shamoon]

#4028

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.