-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working with ShaarliOS client (and maybe other apps ?) #39
Comments
(sorry, misclick) Please give the issue a proper name next time, this one isn't very eloquent :) |
I don't know about Shaarlier. How is you app working ? Where is it searching the API ? |
that's the client software mentioned in #13
Login fails because it can't find the login form inside the html (and needs it for CSRF tokens).
Tomorrow I will ask my user who has the issue, if you may know the endpoint FQDN.
If both the https://github.com/mro/Shaarli-API-test/blob/master/tests/test-login-ok.sh and https://github.com/mro/Shaarli-API-test/blob/master/tests/test-post.sh complete successfully we're ok with the sunshine case. Does that make sense? Currently I'm redesigning the access and shall add a API facade that hides the shaarli peculiarities and exposes the pinboard/delicious API. https://github.com/mro/Shaarli-API-test/blob/develop/openapi.yaml – but this may take months to complete. Essentially the yunohost SSO login seems to get in the way. |
Is that shaarli instance public ? (accessible without the SSO) |
No. This may be the issue, I ask the bugreporter to make shaarli public.
|
Well, I suppose it has to be public to use the API. |
The app needs to be public. Otherwise you have to add the api link to public manually in /etc/ssowat/conf.json.persistent |
@lapineige |
As replied in #40, sorry, my bad, indeed it's implemented. |
Thank you very much @lapineige and @anmol26s ! |
A user of my https://github.com/mro/ShaarliOS just has reported the same issue.
How's the situation with other clients like e.g. https://github.com/dimtion/Shaarlier ?
The text was updated successfully, but these errors were encountered: