-
Notifications
You must be signed in to change notification settings - Fork 0
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
Make RestAPI access work out of the box #9
Comments
Can you check the apache access.log file and see if ident worked? The second field of the log line should be your user id and this id should exist on your vagrant oar frontend/api. Exemple here with docker: Also check that you have enabled mod_ident (a2enmod ident). |
OK, the problem is that I try to access the API from a browser running AJAX that runs on the host and not the frontend (even if the website is on the frontend). So maybe a simple LDAP service with a default host would be the right way to do it because even if I make ident work it will not be the common use case. |
Yes, a simple basic htpasswd file auth is even simpler than an ldap_auth... |
Yes I saw this on the doc but there is no example on the conf file so I wonder if it is still supported? |
For oar-vagrant, NIS is in charge of sharing the user accounts among frontend and node(s). Googling "X_REMOTE_IDENT htpasswd" gets back to us ;-) |
You can try something like that:
(the Rewrite part may be useless actualy)
|
OK, I cannot manage to make the authentication work and I think it is an apache configuration problem. |
I'm triing to work with the Rest API but I got trouble to authenticate to the frontend. I have to add an ident daemon on my laptop + add my laptop address on the
Allow from 192.168.35.1
of the apache config but still I get this strange error:{
"message" : "Oardodo error: 52: [OARDODO] ERROR: Cannot get user to become information (Success)\n\n",
"title" : "Permission denied",
"code" : 401
}
Any idea how to go through this or even a better way to allow my laptop to access automatically?
The text was updated successfully, but these errors were encountered: