Description of problem: When a user has only a single role having one the values 'user', 'developer' or 'manager' then he is not able to access the dashboards. SSO will fail and no other attempt to log in will succeed. Steps to Reproduce: 1. create a user (e.g. username: test, roles: manager) 2. log into business-central 3. click 'dashboards' -> 'business dashboards' or 'process and task dashboards' Actual results: SSO will fail Expected results: SSO success
This is caused by a productization misconfiguration in ER5 build. ER5 is not using the right dashbuilder artifact and that's why the expected roles are not available: admin, analyst, manager, developer, user. Take a look to the following related BZs to figure out the details: https://bugzilla.redhat.com/show_bug.cgi?id=1026249 https://bugzilla.redhat.com/show_bug.cgi?id=1005981 Therefore, we can close this BZ since no issues with roles are expected in ER6 as long as productization builds are well done.
This should be the same and have been resolved as https://bugzilla.redhat.com/show_bug.cgi?id=1026249. *** This bug has been marked as a duplicate of bug 1026249 ***
Please do not close this issue. Rather move it to ON_QA when the build will contain the correct dashbuilder bits. BZ-1026249 impacts EWS as opposed to this issue which impacts EAP. IMO it makes sense to verify that the issue has been fixed on an EAP build. Thank you.
Ryan, does ER7 contain the correct dashbuilder bits? Thanks! Regards Marek
Ah, sorry, my bad to close it. I thought it is the same issue as bug 1026249. ER7 contains the correct dashbuild bits.(ie the jbpm-dashboard component binary and configuration). let me move it to ON_QA for verification. (In reply to Marek Baluch from comment #3) > Please do not close this issue. Rather move it to ON_QA when the build will > contain the correct dashbuilder bits. > > BZ-1026249 impacts EWS as opposed to this issue which impacts EAP. IMO it > makes sense to verify that the issue has been fixed on an EAP build. > > Thank you.
This issue is still present in ER7. However, I believe it will be fixed in next release, because basically the same issue has been reported for ER7 and has already been processed by engineering - see Bug 1047893
Indeed, this was a side effect of the branding procedure. It was fixed some days ago so the fix it will be present in ER8.
Ok, verified with BPMS 6.0.0 CR1