YouTrack 6, Permissions Issue
Hello,
We have a local installed instance of YouTrack 6. It has been updated from version 5 few days ago.
When I'm trying to Grant Role in Project for User or Group I'm getting this error:
"CREATE JetPassProjectRole [null] is forbidden"
I would appreciate for any help in this matter.
Thanks.
We have a local installed instance of YouTrack 6. It has been updated from version 5 few days ago.
When I'm trying to Grant Role in Project for User or Group I'm getting this error:
"CREATE JetPassProjectRole [null] is forbidden"
I would appreciate for any help in this matter.
Thanks.
Please sign in to leave a comment.
Did you manage permissions in YouTrack after upgrade? Was it for root user?
Thank you.
The new permissions is a disaster sadly.
Please can you give an update on when this issue is likely to be resolved or if you need futher information to investigate please ask.
Thank you for your patience!
I kindly ask you to try the latest build (jetbrains.com/youtrack), the problem should be fixed.
Let me know if still remains.
Did you grant roles under root user? May it be the case, you've disabled some permissions for your root account? Could you please restart YouTrack with 'jetbrains.charisma.restoreRootPassword' http://confluence.jetbrains.com/display/YTD6/YouTrack+Start+Java+Parameters ?
Thank you.
Just restart YouTrack with mentioned parameter and log in as root with:
login:root
pswd:root
No. That's one-time reproducible issue.
I am trying to make it so that I can say 'User X should see Project Y.' Never guessed that would take hours spread out over a week plus. The User management really is totally nuts.
I have other error in the same place at now (Selected permissions cannot be granted in this project) and this is true if I shall try to create new projects with new groups and users.
YouTrack version youtrack-6.0.12223.
Installed on local server with ubuntu 12.04.
Got the original "CREATE JetPassProjectRole [null] is forbidden" error, upgraded to the latest version and now have the error "Selected permission cannot be granted in this project", Also tried developer role in the Global project and get the same error.
Tried to log in with root instead of my login (which has Global Admin role), but when i log in with root it says "User is banned", I go on to the root profile, it said "User is banned" I pressed the unban user button. Now it says "User is not banned" in the profile. However when I try to log in with root it still says "User is banned".
Regardless, i have the same issue as the above about granting access to a group or user.
Any help would be appreciated.
I can send you database dump to help reproduce this issue. This problem as I understand near database migration, because on clean db it's work fine.
You can grant access under the Global Admin (root), but you can't do it with a normal Admin.
Not root admin In youtrack 5 could do this, as I understood.
You have to add again global admin rights to not root admin (do it under root admin), if you don't want to login under root admin all the time.
I suspect that not all rights were granted in migration form 5 to 6.
I've managed to get in under root and noticed that root has a "System Admin", that my old admin account does not have, i've added myself as a "System Admin" under all projects and now I can assign roles correctly.
Meanwhile the launchd log has a bunch of exceptions in it:
12:16:07,987 DEBUG [RingLifecycleListener ] [init servlet ] [] Syncing roles...
12:16:07,993 DEBUG [RingLifecycleListener ] [init servlet ] [] Syncing user groups...
12:16:08,115 INFO [security ] [qtp186276003-58] [] [YouTrack[...]] Collected changes
Update by YouTrack[...] @2014-12-04T12:16:08.110-0800
Updated: JPUserGroup[56ce68c8-c998-410a-8d25-54e996e13ead](New Users)
autoJoin[boolean]: true -> false
12:16:08,149 INFO [security ] [sSaverProcessor] [] [internal] Change collection suspended
12:16:08,218 DEBUG [RingLifecycleListener ] [init servlet ] [] Syncing user accounts...
12:16:08,233 WARN [BaseExceptionMapper ] [qtp186276003-58] [] REST exception for URL: /hub/api/rest/users/byname/default_admin_name
I have been using a broken, crippled system now since the 6 upgrade. Is there any way to fix this??? I am sick of wasting time on known bugs...
Thanks!!