Displaying 6 results from an estimated 6 matches for "gssapi_pac".
2013 Jan 21
1
Using samba4 with kerberos outside of an AD realm
...= system keytab
However, whenever I try to access the samba server, the client fails to 
connect. I can see that a ticket has been issued for 
cifs/hostname at MYREALM.COM, but in /var/log/messages I get this:
Jan 21 11:27:00 elastic smbd[1573]: [2013/01/21 11:27:00.675545,  0] 
../auth/kerberos/gssapi_pac.c:116(gssapi_obtain_pac_blob)
Jan 21 11:27:00 elastic smbd[1573]:   obtaining PAC via GSSAPI 
gss_get_name_attribute failed: The operation or option is not available 
or unsupported: No such file or directory
Jan 21 11:27:07 elastic smbd[1574]: [2013/01/21 11:27:07.559656,  0] 
../auth/kerberos/gss...
2024 Jul 09
2
session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
...This problem has come back for me and I can't seem to get around it.
When I try to access a share, I get this error:
session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
Here's what I have in the logs (samba-4.20.1-1.el9.x86_64):
[2024/07/09 11:22:26.747013,? 3] 
../../auth/kerberos/gssapi_pac.c:120(gssapi_obtain_pac_blob)
 ? gssapi_obtain_pac_blob: obtaining PAC via GSSAPI 
gss_get_name_attribute failed: The operation or option is not available 
or unsupported: No such file or directory
[2024/07/09 11:22:26.747103,? 1] 
../../auth/gensec/gensec_util.c:70(gensec_generate_session_info_pac...
2024 Jul 09
2
session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
...'t seem to get around it.
> 
> When I try to access a share, I get this error:
> 
> session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
> 
> Here's what I have in the logs (samba-4.20.1-1.el9.x86_64):
> 
> [2024/07/09 11:22:26.747013,? 3] 
> ../../auth/kerberos/gssapi_pac.c:120(gssapi_obtain_pac_blob)
>  ? gssapi_obtain_pac_blob: obtaining PAC via GSSAPI 
> gss_get_name_attribute failed: The operation or option is not
> available or unsupported: No such file or directory
> [2024/07/09 11:22:26.747103,? 1] 
> ../../auth/gensec/gensec_util.c:70(gensec_g...
2024 Jul 09
1
session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
...can't seem to get around it.
>
> When I try to access a share, I get this error:
>
> session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
>
> Here's what I have in the logs (samba-4.20.1-1.el9.x86_64):
>
> [2024/07/09 11:22:26.747013,? 3] 
> ../../auth/kerberos/gssapi_pac.c:120(gssapi_obtain_pac_blob)
> ? gssapi_obtain_pac_blob: obtaining PAC via GSSAPI 
> gss_get_name_attribute failed: The operation or option is not 
> available or unsupported: No such file or directory
> [2024/07/09 11:22:26.747103,? 1] 
> ../../auth/gensec/gensec_util.c:70(gensec_g...
2024 Jul 09
1
session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
...> When I try to access a share, I get this error:
> > 
> > session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
> > 
> > Here's what I have in the logs (samba-4.20.1-1.el9.x86_64):
> > 
> > [2024/07/09 11:22:26.747013,? 3] 
> > ../../auth/kerberos/gssapi_pac.c:120(gssapi_obtain_pac_blob)
> >  ? gssapi_obtain_pac_blob: obtaining PAC via GSSAPI 
> > gss_get_name_attribute failed: The operation or option is not
> > available or unsupported: No such file or directory
> > [2024/07/09 11:22:26.747103,? 1] 
> > ../../auth/gensec/...
2024 Jul 09
1
session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
...gt;>
>> When I try to access a share, I get this error:
>>
>> session setup failed: NT_STATUS_NO_IMPERSONATION_TOKEN
>>
>> Here's what I have in the logs (samba-4.20.1-1.el9.x86_64):
>>
>> [2024/07/09 11:22:26.747013,? 3]
>> ../../auth/kerberos/gssapi_pac.c:120(gssapi_obtain_pac_blob)
>>   ? gssapi_obtain_pac_blob: obtaining PAC via GSSAPI
>> gss_get_name_attribute failed: The operation or option is not
>> available or unsupported: No such file or directory
>> [2024/07/09 11:22:26.747103,? 1]
>> ../../auth/gensec/gensec...