Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't add new access path #56

Open
xqvier opened this issue Jan 11, 2014 · 9 comments
Open

Can't add new access path #56

xqvier opened this issue Jan 11, 2014 · 9 comments
Assignees
Labels
Milestone

Comments

@xqvier
Copy link

xqvier commented Jan 11, 2014

Hi,

First thing first, great job on that tool. It's really usefull.

I have a problem adding access path via the UI.
It says : "You don't have the permission to create this access path: test:/"

So here is the problem :

  • I have all roles enabled for my user
  • data directory and all files have 777 rights
  • SVNAuthFile has authorization
  • When i create a new repository it write the new line [test:/] in the SVNAuthFile. It seems it should write [/test] (as seen for previous well managed repo), I might be wrong here.
  • The file data/userroleassignments.ini isnt updated with the line #=/test
  • Of course if I manually edit the 2 previous files, the access-path appears in the list and i can edit permissions.

Maybe I'm missing something here but if you could drive me towards a solution I'd be glad !

Thanks.

@ghost ghost assigned mfreiholz Jan 12, 2014
@xqvier
Copy link
Author

xqvier commented Mar 14, 2014

Hello again,

I get back to you because u labeled this as support but i never heard of you !
I still have the problem so i was wondering what i was doing wrong.

If you can give me a heads up.

Thanks

@mfreiholz
Copy link
Owner

Hi sorry, i forgot about this issue.
Did you check the apache logs? Maybe some error can be found there.

The entry [test:/] is right.

Maybe it has something todo with the Project Manager settings. Do you use Project-Manager settings in your configuration?

@ghost
Copy link

ghost commented Mar 25, 2015

Can you tell me whether the problem solved, I also met the same problem, see the apache logs, no error in log

@mfreiholz
Copy link
Owner

Can you post your "config.ini" file and some common system specs, please? I'd like to reproduce this problem.

@ghost
Copy link

ghost commented Mar 25, 2015

[Common]
FirstStart=0
BackupFolder=./data/backup/

[Translation]
Directory=./translations/

[Engine:Providers]
AuthenticationStatus=basic
UserViewProviderType=passwd
UserEditProviderType=passwd
GroupViewProviderType=svnauthfile
GroupEditProviderType=svnauthfile
AccessPathViewProviderType=svnauthfile
AccessPathEditProviderType=svnauthfile
RepositoryViewProviderType=svnclient
RepositoryEditProviderType=svnclient

[ACLManager]
UserRoleAssignmentFile=./data/userroleassignments.ini

[Subversion]
SVNAuthFile=/var/www/svnconfig/accessfile

[Repositories:svnclient]
SVNParentPath=/var/www/svn
SvnExecutable=/usr/bin/svn
SvnAdminExecutable=/usr/bin/svnadmin

[Users:passwd]
SVNUserFile=/var/www/svnconfig/passwdfile

[Users:digest]
SVNUserDigestFile=
SVNDigestRealm=SVN Privat

[Ldap]
HostAddress=ldap://192.168.136.130:389/
ProtocolVersion=3
BindDN=CN=Manuel Freiholz,CN=Users,DC=insanefactory,DC=com
BindPassword=root
CacheEnabled=false
CacheFile=./data/ldap.cache.json

[Users:ldap]
BaseDN=DC=insanefactory,DC=com
SearchFilter=(&(objectClass=person)(objectClass=user))
Attributes=sAMAccountName

[Groups:ldap]
BaseDN=DC=insanefactory,DC=com
SearchFilter=(objectClass=group)
Attributes=sAMAccountName
GroupsToUserAttribute=member
GroupsToUserAttributeValue=distinguishedName

[Update:ldap]
AutoRemoveUsers=true
AutoRemoveGroups=true

[GUI]
RepositoryDeleteEnabled=false
RepositoryDumpEnabled=false
AllowUpdateByGui=true

@mfreiholz
Copy link
Owner

Oh and your ./data/userroleassignments.ini aswell, please. (As long as there isn't any critical information inside).

I will check this tonight.

@ghost
Copy link

ghost commented Mar 25, 2015

./data/userroleassignments.ini:
[admin]
Administrator=

[admin:AccessPaths]
0=longtu_operationproject:/


env information:
centos-6.5
php-5.4.36

apache-2.2.15

Thank you so much~

@mfreiholz
Copy link
Owner

I think i found the problem.
If you set the user "admin" as project-manager of repository "longtu_operationproject:/", he is not longer able to create access-paths for any other repository.

Workarround
Do not set the your administrators as project-managers. They already have access to everything.

I don't think that i will fix this for the current version.
=> Will be fixed with V2.

@mfreiholz mfreiholz added this to the Version 1.7.0 milestone Mar 25, 2015
@ghost
Copy link

ghost commented Mar 26, 2015

Ok, thank you very much

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants