bug #7529
closed
Wrong UUID after creating a GrantedAuthority for a Role like ROLE_PUBLISH
Added by Andreas Kohlbecker almost 6 years ago.
Updated almost 3 years ago.
Description
The ROLE_PUBLISH was not yet in the database and thus was created using the Taxeditor GrantedAuthority Create Dialog.
The resulting GrantedAuthority in the database has the wrong uuid:
72 | 2018-07-03 07:29:27 | 0ada8cd5-8cdd-4fc0-a329-59d4d122008a | ROLE_PUBLISH
the Role has a different uuid in the code:
public final static Role ROLE_PUBLISH = new Role(UUID.fromString("9ffa7879-cc67-4592-a14a-b251cccde1a7"), "ROLE_PUBLISH");
Check if the ROLE_PUBLISH is being used in a DB with wrong uuid
I am not sure if this is a taxeditor issue or if the cdmlib methods are missing to handlde this correctly. But first of all we should take a look at the taxeditor.
- Tags set to fast
- Description updated (diff)
- Priority changed from New to Highest
- Target version changed from Unassigned CDM tickets to Release 5.21
AK, do you still remember the context for this ticket. What did not work, what did you test, which DB was involved?
I seem to remember that I created this ticket in turn to an email conversation that the both of us had.
However, I don't remember 100% exactly the situation, but it was like that someone created the ROLE_PUBLISH via the Groups-Details editor, or the like.
In this case a new GrantedAuthotrity with a new UUID is being created. This UUID conflicts with the one which is predefined in the class eu.etaxonomy.cdm.persistence.permission.Role.
So the solution to this would be that what I suggested in the email conversation today:
"Wir sollten eine Default-Gruppe "Publish" einführen, die durch den FirstDataInserter angelegt wird und die die ROLE_PUBLISH als einzige GrantedAuthority enthält. Dadurch befindet sich die Rolle dann auf jeden Fall in jeder Datenbank und kann per Gruppe leicht einem User zugewiesen werden."
- Description updated (diff)
- Assignee changed from Andreas Müller to Andreas Kohlbecker
- Target version changed from Release 5.21 to Release 5.20
- Status changed from New to Resolved
- % Done changed from 0 to 50
- Status changed from Resolved to Closed
- % Done changed from 50 to 100
verified at some test databases: works as expected.
- Category changed from taxeditor to cdmlib
Have you also checked that no ROLE_PUBLISH with wrong UUID exists in existing production DBs? (see ticket description)
Andreas Müller wrote:
Have you also checked that no ROLE_PUBLISH with wrong UUID exists in existing production DBs? (see ticket description)
Yes of course otherwise I wouldn't have closed the ticket.
Also available in: Atom
PDF