Skip to main content
Solved

RDM REST API (v14.3 or later)

may_kwok
Star Blazer L3
Forum|alt.badge.img+4

Hello hive mind,

Has anyone out there who have RDM v14.3 or later, and successfully used the new RDM REST API feature?

We’ve upgraded our dev environment to v14.5.1 this week, I tried the REST API, and it keeps returning with “java.lang.Exception: org.springframework.security.access.AccessDeniedException: Cannot access entity: address_type” error. (Was trying to query my entity called address_type)

I ensured my service account client has full access to the table. That service account client calls other API endpoints that I have built before on rdm-server and that authenticates fine.

I wonder what I’m missing. Anybody successful before and we can compare notes?

Thanks!

Best answer by Mario Georgiev

Hello May,


Please check the following things:

 

  • The services account has a correct prefix in front of its name. It should start with RDM_
  • The correct roles were assigned in the Service accounts roles for the client in Keycloak
  • This role has correct permissions in the RDM web application permissions tab
View original
M
1 person likes this
  • M
    Mario Georgiev
Did this topic help you find an answer to your question?

4 replies

M
Ataccamer
Forum|alt.badge.img+2

Hello May,


Please check the following things:

 

  • The services account has a correct prefix in front of its name. It should start with RDM_
  • The correct roles were assigned in the Service accounts roles for the client in Keycloak
  • This role has correct permissions in the RDM web application permissions tab
A
Ataccamer
Forum|alt.badge.img+2
  • AKislyakovAtaccamer
  • Ataccamer
  • 146 replies
  • February 9, 2024

In addition to what Mario wrote it could be issue with permission sync. Please check that you see the service account user with appropriate roles in the Users part of the RDM web application permissions tab.

M
1 person likes this
  • M
    Mario Georgiev
may_kwok
Star Blazer L3
Forum|alt.badge.img+4
  • may_kwokStar Blazer L3
  • Author
  • Star Blazer L3
  • 82 replies
  • February 9, 2024

So we found out that my token client did not have “rdm” in the name.

Once we created a new token client starting with “rdm” it worked.

I was blind and did not see that part in the documentation.

Thanks folks for the help!

M
Cansu
2 people like this
  • M
    Mario Georgiev
  • Cansu
    Cansu
Cansu
Community Manager
Forum|alt.badge.img+3
  • CansuCommunity Manager
  • Community Manager
  • 625 replies
  • February 12, 2024

Great to hear everything is resolved now @maykwok_hamilton 😊

Check out our Quick Start Guide to get started on the community 🙋‍♀️

Reply


Most Liked this week

Community Terms of Use & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings