DevConnect Limit API Product by Role module issue

We are using 4.18.05 dev portal and observed DevConnect Limit API Product by Role module doesn't work. It is somekind of UI bug which it never saves properly and doesn't enable the product to allocated user(as per the role).

Similar question was asked in below post

https://community.apigee.com/questions/23910/is-it-possible-to-retrict-list-of-products-in-the.html

Any work around?

Support Case # 1459748 opened(providing the snapshots) and waiting on support response.

Thanks.

Solved Solved
0 9 239
1 ACCEPTED SOLUTION

UPDATE 2019 March 4

The behavior you are seeing is the result of a bug in the DevConnect Limit API Product by Role module. There is an alternative module that allows you to work around the bug.

Get it here, from my repo:

https://github.com/DinoChiesa/Edge-DevPortal-ApiProducts-Access-Extended

I cannot directly fix the _original_module. I have filed a bug.


ORIGINAL ANSWER

Maybe try this module?

https://github.com/DinoChiesa/Edge-DevPortal-ApiProducts-Access-Extended

It originated as a fork of the builtin devconnect API Product Access module.

The "extended" module supplants the original module, provides a few enhancements and improvements.

  • "default" access for an API Product.
  • better Admin UI form

If you use this module, you should disable the other module.

View solution in original post

9 REPLIES 9

Did any one experienced the issue & is there a work around ?

UPDATE 2019 March 4

The behavior you are seeing is the result of a bug in the DevConnect Limit API Product by Role module. There is an alternative module that allows you to work around the bug.

Get it here, from my repo:

https://github.com/DinoChiesa/Edge-DevPortal-ApiProducts-Access-Extended

I cannot directly fix the _original_module. I have filed a bug.


ORIGINAL ANSWER

Maybe try this module?

https://github.com/DinoChiesa/Edge-DevPortal-ApiProducts-Access-Extended

It originated as a fork of the builtin devconnect API Product Access module.

The "extended" module supplants the original module, provides a few enhancements and improvements.

  • "default" access for an API Product.
  • better Admin UI form

If you use this module, you should disable the other module.

Tried the new module and see same UI issue.Updated the case with snapshots.

What do you mean by "same UI issue" ?

I am looking at a screen that shows "The configuration options have been saved".

What leads you to conclude that the save particularly is not working? Are you saying that it is impossible to tick the box next to one of the products? Are you saying that you tick the box, but after saving, the box becomes unticked again? I'm not clear.

Some suggestions:

  1. Judging from the screenshot, when you use the Extended Access control module, you also need to tick the box that says "Access check enabled". This is the master switch. You need to turn it on! 🙂
    Also, be sure to disable the other module if you choose to use this one.
  2. In either case, whether you use the original module or the extended one, turn off caching or "flush all caches" in Drupal before testing it out.

Hello Dino,

Thanks for quick response..

When we choose product for administrator and internal role & choose save ,the box becomes unticked again.

Also when we choose Access check enabled after enabling product & perform flush all caches in drupal it doesn't show at all to anyone.

If we untick "Access check enabled" it is visible to all 😞

Uploaded new snapshots to case as well..

-Vinay

I think I see... I've reproduced the problem here. Maybe the product name that contains a dot and a dash is affecting the behavior of the UI. I will investigate.

ok, Vinay. Can you get the latest updates of that "extended" module?

I was able to reproduce the problem here. I've made a change and now it works for me. I pushed that change to the github repo. You need to grab that change and then push that to your drupal site. Refresh all caches and then try again with the admin panel.

Thanks Dino(you are just amazing). It works now. Appreciate your help.

Glad to help. BTW, to get the fix you must use the extended module (from my repo).

I cannot fix the _other_module. I will file a bug, though.