API/V2/members not working using Java

Hi,

I am trying to retrieve member information about a specific member using the /api/v2/members method of the api using Java code. I can retrieve the otcs ticket with /api/v1/auth. Using that ticket, I'm able to retrieve member info about the authenticated user using /api/v1/auth and server info using /api/v1/serverinfo.

For the members call, I'm using the parameter where_name=****. I pass that parameter the same way I pass the user id and password parameters to get the authentication ticket. When I do that I get this error: "Could not process object, invalid action 'create'."

If I pass the where_name as part of the URL, there is no error, but it seems to be ignored and I get back a semi-complete list of users. Note that the where_type parameter works with members but as part of the URL.

Has anyone had success with the api/v2/members call?

Thanks.

Find more posts tagged with

Comments

John Simon

Did you include the where_type as well? I have not looked at the code but I would imagine if you pass a name it needs to know the type (so it knows if you are looking for groups or users).
Cheers...

Frank K

@John Simon said:
Did you include the where_type as well? I have not looked at the code but I would imagine if you pass a name it needs to know the type (so it knows if you are looking for groups or users).
Cheers...

I tried running it with both where_name and where_type parameters but with no luck. Using just where_type by itself seemed to work.

After I posted this question, a person at OpenText support said that the API/V2/members method doesn't even work. I'm not sure why it would be documented in the API if it doesn't work.

Thanks,
Frank

John Simon

Do you know the ID of the member? I tried api/v2/members/{ID} and get an error ("The REST API Url could not be found in the mappings registry") which is the error you get when that particular call has not been implemented (I am on 16.2). But api/v1/members/{ID} works
Cheers...

Frank K

@John Simon said:
Do you know the ID of the member? I tried api/v2/members/{ID} and get an error ("The REST API Url could not be found in the mappings registry") which is the error you get when that particular call has not been implemented (I am on 16.2). But api/v1/members/{ID} works
Cheers...

All we have is a user's name, so we were planning to use that in the member call to get the id. The only member info I can get is the when using the get /api/v1/auth call, which brings back the member id of the authenticated user. I've used that to get member info, but only as a test. We are not interested in the member info of the authenticated user since it's just a generic one.

Thanks

Appu Nair

As a workaround of sorts you can try calling rest against a WR with a LR tied that gives you that info

Select * from KUAF where name like within quotes the name

Now once OT gives you something to work with you could still advance your project?

John Simon

As Appu said you could use a WebReport for now. You would pass in the username and have it return whatever you like. If not an option for you and you are open to customization, we can implement that REST call for you.
Cheers...

Frank K

@John Simon said:
As Appu said you could use a WebReport for now. You would pass in the username and have it return whatever you like. If not an option for you and you are open to customization, we can implement that REST call for you.
Cheers...

OpenText support told us about the method {otdsws}/rest/authentication/credentials to get the ticket and then call …/rest/users/{userid}/memberof to find the rest of the user info. When I try to get the ticket using Java code, I get a "405 Method not Allowed" response from the server.

It works for the support person using the "Try it out" button on the Rest API UI and also with Postman. In the REST API UI I can get the ticket, but the memberof call doesn't work for me. We are using a browser with restrictions and we have no access to Postman for security reasons.

John Simon

It depends on your version of content server. It may well work for OT support as they may be on a newer version. I am on 16.2.2 and I do not see "users" implemented as a REST call (I checked the registry and it is not there). There is a v1/members and a v2/members. v1/members/{id} allows you to get info about a user but you have to know the id (from kuaf). The documentation shows that v2/members/{id} should work but that does not work for me (not implemented). Based on what you have said your best bet is going to be using a REST call to a WebReport that accepts your username and returns whatever info you want in a JSON string.
Cheers...

Matthew_Pinkney

Hello,
The documentation posted on the KC and developer.opentext.com reflect the current release's APIs, so it will likely have more than what an older version of Content Server has.
api/v2/members/id was added in 16.2.3.

api/v2/members/ has been around since the initial 16.2.0 and should work for you.

Frank, it sounds like you could be using a POST and or passing the where_name in the body instead of using a GET and passing the where_name in the query string. That would account for it being ignored or getting a create error.

HFCDev

Just to add to this, I was a bit surprised when I read that a request works in Postman but not in Java. That to me says that there is something wrong with the way the Java code is implementing the call. In these scenarios, Fiddler 4 is your friend. If you are in a DEV environment, using Fiddler is easiest if you can have your server accept http instead of https, otherwise you have to install Fiddler's self-signed certificate so it can decode traffic for you (you may or may not have permission to do that on your machines).
-Hugh

Frank K

I abandoned the /api/v1/members method and am using /otdsws/rest/users/{username}/memberof method. It looks like it should provide the information we need. I couldn't get the authentication/credential to work because I was using the wrong input. Once I changed it to a json it worked and I could get a ticket. Now with the ticket, I used it with memberof and it works as well.

Thank you all for your help.

John Simon

My bad, I just noticed you are using the OTDS REST calls not the CS REST calls. No wonder I couldn't find /users/... Glad to hear you have it sorted.
Cheers...