Project

General

Profile

Actions

bug #7529

closed

Wrong UUID after creating a GrantedAuthority for a Role like ROLE_PUBLISH

Added by Andreas Kohlbecker over 4 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
Highest
Category:
cdmlib
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Severity:
normal
Found in Version:

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.

Actions #1

Updated by Andreas Müller almost 2 years ago

  • 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?

Actions #2

Updated by Andreas Kohlbecker almost 2 years ago

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."

Actions #3

Updated by Andreas Kohlbecker almost 2 years ago

  • Description updated (diff)
Actions #4

Updated by Andreas Müller almost 2 years ago

  • Assignee changed from Andreas Müller to Andreas Kohlbecker
Actions #5

Updated by Andreas Kohlbecker almost 2 years ago

  • Target version changed from Release 5.21 to Release 5.20
Actions #6

Updated by Andreas Kohlbecker almost 2 years ago

  • Status changed from New to Resolved
  • % Done changed from 0 to 50
Actions #7

Updated by Andreas Kohlbecker almost 2 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 50 to 100

verified at some test databases: works as expected.

Actions #8

Updated by Andreas Kohlbecker almost 2 years ago

  • Category changed from taxeditor to cdmlib
Actions #9

Updated by Andreas Müller almost 2 years ago

Have you also checked that no ROLE_PUBLISH with wrong UUID exists in existing production DBs? (see ticket description)

Actions #10

Updated by Andreas Kohlbecker almost 2 years ago

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.

Actions #11

Updated by Andreas Müller over 1 year ago

  • Tags deleted (fast)
Actions

Also available in: Atom PDF