cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Community Tip - You can Bookmark boards, posts or articles that you'd like to access again easily! X

Unable to disable the active user from Codebeamer via the REST API

RK_8650
10-Marble

Unable to disable the active user from Codebeamer via the REST API

Hi Team, I'm trying to disable the active user from codebeamer via REST API as mentioned in codebeamer wiki using
https://codebeamer.com/cb/wiki/117612#section-Update+an+existing+user.
It works when the user is not the only project admin of a project, whereas when the user is only project admin of a project, disabling of such user also shows successful response code 200. I would have expected an error response code from RESTAPI, since it didn't disable the user. Trying the same scenario from Web UI, it shows the below error message. User [10] MME1COB cannot be disabled as he or she is the only Project Admin in the following project(s): [22] BD Test1 Project. Could you please log this as a defect and fix them ?

ACCEPTED SOLUTION

Accepted Solutions
alfonso_c
14-Alexandrite
(To:RK_8650)

I found the topic also documented here: https://www.ptc.com/en/support/article/CS413687

 

Indeed, the current legacy V1 is in maintenance mode. Hopefully, a fully functional behavior will be provided on Swagger V3 in the future.

View solution in original post

2 REPLIES 2
RK_8650
10-Marble
(To:RK_8650)

Implement missing Swagger API to update the user in Codebeamer similar to rest api https://codebeamer.com/cb/wiki/117612#section-Update+an+existing+user.

 

Note: Currently there is a known bug on this rest api. When the user is only project admin of a project, disabling of such user also shows successful response code 200 but not disabled. In this case it should have reported an error. While implementing the Swagger API please consider this use case.

alfonso_c
14-Alexandrite
(To:RK_8650)

I found the topic also documented here: https://www.ptc.com/en/support/article/CS413687

 

Indeed, the current legacy V1 is in maintenance mode. Hopefully, a fully functional behavior will be provided on Swagger V3 in the future.

Announcements



Top Tags