Hi all
So, I am creating this Liferay portal content in my job. Part of the task is to create a large number of dynamic data lists, that will change frequently. Since Liferay does not support bulk import of DDL data and manual input is just impractical, I decided to use the JSON Web service functionality, namely the HTTP request. I encountered several problems along the way.
1) There is a nice bug in the JSON web interface. When you input the parameters and generate the HTTP request, its is missing a single letter, namely in the parameter record-set-i D . This generates the "No JSON web service action associated with path XXX and method GET for /" exception.
I trusted you Liferay, and you let me down
2) There is no official documentation on how to construct the security element of the HTTP request. Incorrect element generates the "Authenticated access required" exception. The answer to this can be found here:
http://www.liferaysavvy.com/2015/03/liferay-json-web-services-authenticated.html
Kudos to Meera for that blog post.
3) The previous bugs I overcame with a combination of googling and tinkering. But then I came to the "No User exists with the primary key 0" exception for the /ddlrecord/add-record method. I found on the web, this might have something to do with how Liferay detects the user. Namely, it does not pass the user identificator from the header, which remains null, or 0. The DDL record is than not created, since it requires an author.
So far, I don't know how to solve this. Do you have any ideas?
So, I am creating this Liferay portal content in my job. Part of the task is to create a large number of dynamic data lists, that will change frequently. Since Liferay does not support bulk import of DDL data and manual input is just impractical, I decided to use the JSON Web service functionality, namely the HTTP request. I encountered several problems along the way.
1) There is a nice bug in the JSON web interface. When you input the parameters and generate the HTTP request, its is missing a single letter, namely in the parameter record-set-i D . This generates the "No JSON web service action associated with path XXX and method GET for /" exception.
I trusted you Liferay, and you let me down
2) There is no official documentation on how to construct the security element of the HTTP request. Incorrect element generates the "Authenticated access required" exception. The answer to this can be found here:
http://www.liferaysavvy.com/2015/03/liferay-json-web-services-authenticated.html
Kudos to Meera for that blog post.
3) The previous bugs I overcame with a combination of googling and tinkering. But then I came to the "No User exists with the primary key 0" exception for the /ddlrecord/add-record method. I found on the web, this might have something to do with how Liferay detects the user. Namely, it does not pass the user identificator from the header, which remains null, or 0. The DDL record is than not created, since it requires an author.
So far, I don't know how to solve this. Do you have any ideas?
Jan Beran:
Hi all
1) There is a nice bug in the JSON web interface. When you input the parameters and generate the HTTP request, its is missing a single letter, namely in the parameter record-set-i D . This generates the "No JSON web service action associated with path XXX and method GET for /" exception.
I trusted you Liferay, and you let me down
See LPS-50384 *sad face*
2) There is no official documentation on how to construct the security element of the HTTP request. Incorrect element generates the "Authenticated access required" exception. The answer to this can be found here:
http://www.liferaysavvy.com/2015/03/liferay-json-web-services-authenticated.html
Kudos to Meera for that blog post.
Liferay supports industry-standard authentication techniques, one of which is HTTP Basic Authentication
There is also a wikipedia page on it! But basically you have to authenticate for most JSON web services, especially those that change the database.
3) The previous bugs I overcame with a combination of googling and tinkering. But then I came to the "No User exists with the primary key 0" exception for the /ddlrecord/add-record method. I found on the web, this might have something to do with how Liferay detects the user. Namely, it does not pass the user identificator from the header, which remains null, or 0. The DDL record is than not created, since it requires an author.
So far, I don't know how to solve this. Do you have any ideas?
You are probably not constructing the Basic auth header correctly. Does it work with a known-to-work tool, like the unix/linux command line "curl"? For example, on Liferay 6.2 I just created a simple DDL definition using the GUI that contains two text fields (text1, text2). Then used the JSON console to create a new record, and revealed the curl command which works for me:
curl https://my-server.com/api/jsonws/ddlrecord/add-record -u test@liferay.com:MYPASSWORD -d groupId=10182 -d recordSetId=70006 -d displayIndex=0 -d 'fieldsMap={"text1":"foo", "text2": "bar"}'
Ensure you pass the proper groupId and recordSetId (are you?)
This created a new record where text1=foo, text2=bar. Using curl -v revealed the proper header value that it constructed (along with all the other stuff, including verification that I was doing an HTTP POST vs. GET):
POST /api/jsonws/ddlrecord/add-record HTTP/1.1
Authorization: Basic dGVzdEBsaWZlcmF5LmNvbTpNWVBBU1NXT1JE
User-Agent: curl/7.37.1
Host: my-server.liferay.com
Accept: */*
Content-Length: 88
Content-Type: application/x-www-form-urlencodedJan Beran:
Yes, I am indeed using Liferay 6.2 CE.
I am trying to write to a DDL that I have created and am able to put records in, both in the UI. Therefore, I have permission enough.
Is your portal set to use email address (the default) when logging in? If not, then you have to construct the Authorization header using whatever method (screenname for example) you normally use to sign in using the UI.
Any other settings that you might have in a custom portal-ext.properties that might change the way Liferay authenticates or change some JSON web service setting?
If that checks out, then I'd ask you to re-download Liferay Portal 6.2 CE GA4, start it up, and create a super simple DDL definition and DDL, and then try to insert records using that. This worked for me the first and every time using 'test@liferay.com / test' and with no custom portal-ext.properties (and using HSQLD
. You may also try to re-index the search indexes, using Control Panel -> Server Administration -> Reindex all search indexes (Click exceute). Perhaps your user database index is wrong somehow.
