× Requests and support related to jBackend.

persistent login

More
6 years 6 months ago #6421 by phonemas
Replied by phonemas on topic persistent login
Greetings. Me again.

I am developing an app for mobile devices (android & iOS). For now I am generating the apk for android. I am using Corona Labs for development.

The app brings private content from a Joomla CMS system.

The login process (authentication) works well. There I can get the session_id.

But the process of bringing the private content (in the same script) tells me:

{"status": "ko", "error_code": "REQ_MNF", "error_description": "Module not found"}

** It is as if the previous authentication process was closed.

I have tried placing the session_id in the request and the result is the same.

body = "api_key =" .. settings.API_KEY .. "& rootid =" .. settings.cateRootId .. "& session_id =" .. settings.sessionId

I have verified the sent values and they are correct.

The question is: should I have something extra in mind when passing the session information?

Regards,

Solón

Please Log in or Create an account to join the conversation.

More
6 years 6 months ago #6422 by phonemas
Replied by phonemas on topic persistent login
My config module (plugin) user:

JSON LOGIN: yes
JSON Register: NO
Enable session id: yes

Greetings. Me again.

I am developing an app for mobile devices (android & iOS). For now I am generating the apk for android. I am using Corona Labs for development.

The app brings private content from a Joomla CMS system.

The login process (authentication) works well. There I can get the session_id.

But the process of bringing the private content (in the same script) tells me:

{"status": "ko", "error_code": "REQ_MNF", "error_description": "Module not found"}

** It is as if the previous authentication process was closed.

I have tried placing the session_id in the request and the result is the same.

body = "api_key =" .. settings.API_KEY .. "& rootid =" .. settings.cateRootId .. "& session_id =" .. settings.sessionId

I have verified the sent values and they are correct.

The question is: should I have something extra in mind when passing the session information?

Regards,

Solón

Please Log in or Create an account to join the conversation.

More
6 years 6 months ago #6423 by admin
Replied by admin on topic persistent login
Hi Solón,
the error code says something different. It seems you are making a wrong request, or a request to a module not published yet. To have the request you are trying could help.

Kind regards
Luigi

Please Log in or Create an account to join the conversation.

More
6 years 6 months ago #6424 by phonemas
Replied by phonemas on topic persistent login
Hi Luigi.

Based on your response, I was reviewing and found this:

The "jBackend - Content Module" had access only for registered users.

I have configured this module (plugin) with public access and everything works perfectly.

Thank you very much.

Solón

PD: Maybe using the variable session_id (valid) , the Joomla CMS should bypass this restriction? It's just an opinion

Please Log in or Create an account to join the conversation.

More
6 years 5 months ago #6429 by admin
Replied by admin on topic persistent login
Hi Solón,
the session_id is used to mantain the user session (i.e. his authentication status), but this is different from the endpoint access policies (free, user, api key) that is managed centrally by the component. The content plugin has only in charge the content filtering (e.g. if an article is restricted to only registered users).

I hope this makes sense for you.

Kind regards,
Luigi

Please Log in or Create an account to join the conversation.

Time to create page: 0.131 seconds