[Admin-ml] Quand Kerby contrarie AFP...

Fabrice Vincent f.vincent at allibert-trekking.com
Ven 12 Juin 18:22:26 CEST 2009


A+
Fabrice


> De : Jean-Luc Bailloeul <jlbailloeul at irtsnpdc.fr>
> 
> Bonsoir Fabrice,
> 
> Tu as trouvé une solution à ton problème ?
Non....   :'(

> le post suivi sur la liste Apple n'a rien révélé de nouveau. Voici ce
> qu'il en dit :
> 
>> Jim McIntyre wrote:
>> 
>>     I'm having some trouble understanding a permissions issue: AFP
>> group permissions aren't working as expected when I log in to the
>> server using Kerberos.
En effet c'est exactement le même problème !
>> 
>>     I created a new share point that resides on a volume with ACLs
>> enabled. Using the standard permissions inspector in WGM I gave a
>> group named "serveradministrators" read & write access to the share
>> point. I also created an ACL entry for the folder corresponding to
>> the share point, and gave the same group full control. No
>> permissions are granted for any other groups or users except for the
>> folder's owner (an admin account on the server).
Par contre je n'utilise pas les ACL
>> 
>>     When I connect to the server as myself from my workstation (also
>> running 10.4.11), the workstation first asks me to authenticate
>> using Kerberos. If I do that, I can choose to mount the share point,
>> but I'm denied access to opening it after it mounts. The Finder
>> presents a dialog saying "The folder '[name]' could not be opened
>> because you do not have sufficient access privileges." The share
>> point appears on my desktop as a folder with a red circle/minus sign.
>> 
>>     If, however, I cancel the Kerberos login and log in using the
>> standard Finder dialog, I am able to mount and use the share point
>> as intended.
Idem pour moi. 
> 
>> 
>> One person who responded directly mentioned some other folks had the
>> same issue...
>> 
>> I was able to fix the problem by deleting the shared folder on the
>> server, creating a new folder, designating it a share point, and
>> applying the desired permissions. I'm not sure why it worked, but it
>> did.
J'ai le problème aussi sur un partage auquel je n'ai pas touché depuis
plusieurs année... Du coup je ne crois pas a ce genre de "solution"...

Bref, le problème est bien identifié et complètement reproductible, mais pas
de début de commencement de solution en vue !
Je sèche (et apparemment la liste aussi)...  :(






Plus d'informations sur la liste de diffusion Admin-ml