java.lang.SecurityException: Access not allowed for user 'scriptuser (Funktionaler User für Skripte)

Zendesk API User

• 19 mai 2022 09:34

Author: Aradhana
Publication Date: 5/19/2022 9:34

I am using 

getReferences(); method of StoreElement class which is first spirit API class.

But i am getting below exception can anyone have any idea how to solve this:

WARN 19.05.2022 07:28:16.329 (de.espirit.firstspirit.store.access.contentstore.ContentUtil): Failure adapting gid
java.lang.SecurityException: Access not allowed for user 'scriptuser (Funktionaler User für Skripte) (Funktionaler User für Skripte)'
at de.espirit.firstspirit.common.GidAgentImpl.checkAccess(GidAgentImpl.java:464)
at de.espirit.firstspirit.common.GidAgentImpl.adaptGid(GidAgentImpl.java:115)
at de.espirit.firstspirit.store.access.contentstore.ContentUtil.findEntityAndRepairGidRegistry(ContentUtil.java:1023)
at de.espirit.firstspirit.client.access.editor.lists.IndexEditorValueImpl$ValueReferencesJournalImpl.addReferenceToDataset(IndexEditorValueImpl.java:805)
at de.espirit.firstspirit.content.access.GidDatasetIdentity.reportValueReference(GidDatasetIdentity.java:77)
at de.espirit.firstspirit.content.access.DatasetDataAccessSession.reportValueReference(DatasetDataAccessSession.java:474)
at de.espirit.firstspirit.content.access.DatasetDataAccessSession.reportValueReferences(DatasetDataAccessSession.java:463)
at de.espirit.firstspirit.content.access.DatasetDataAccessSession$1.reportValueReferences(DatasetDataAccessSession.java:161)
at de.espirit.firstspirit.client.access.editor.lists.IndexEditorValueImpl.findReferences(IndexEditorValueImpl.java:434)
at de.espirit.firstspirit.client.access.editor.lists.IndexEditorValueImpl.findReferences(IndexEditorValueImpl.java:85)

Any help on same would be appreciate.

Thank you in advance. 

 

0

• 

  Zendesk API User

  • 19 mai 2022 10:28

  Author: hoebbel - 5/19/2022 10:28
  

  Dear Aradhana,

  at least one of the references (generated from a FS_INDEX component) points to a dataset that either has no or not the expected FS_GID.

  That you get this exception could be a bug. Please create a ticket for our TechSupport. If possible, provide the information, which dataset or database causes the problem. (I remember a very similar issue with a read-only database).

  Best regards
  Holger

  0

Vous devez vous connecter pour laisser un commentaire.