[OpenAFS] Windows 10 Pro and openafs client : cannot obtain token

Andreas Ladanyi andreas.ladanyi@kit.edu
Mon, 17 Jun 2019 12:11:57 +0200


Hi Laurent,

i had similar problems in the past.

The "best practise" solutions was to only install the Auristor package
which delivers also the Heimdal client.

I didnt install the Network ID Manager.


To avoid the AFS login failed message (if you will get one in the
future) after windows restart have a look at this page:

https://www.tenforums.com/tutorials/49963-use-sign-info-auto-finish-after-update-restart-windows-10-a.html


Andreas


> Hi,
>
> I'm facong problems to obtain AFS token on WIndows 10 Pro computer
> integrated in a Windows Server 2016 domain.
> Configuration :
> Windows 10 Pro 1809,
> Heimdal 7.4.040
> Netwwork Identity Manager 2.5.0.106
> OpenAFS 1.7.3301 from Auristor
>
>
> Network Identity Manager obtains kerberos ticket well not the AFS one.
>
> aklog -d (in terminal) outputs
>
> Authenticating to cell CELLNAME
> Getting v5 tickets: afs/CELLNAME@REALM
> aklog: Couldn't get afs/CELLNAME@REALM ticket: Matching credential
> (afs/CELLNAME@REALM) not found
>
> Credentials exists
> It works perfectly under Windows 7 with both OpenAFS 1.7.3301 and
> OpenAFS 1.5.99.06 client.
>
> Thanks in advance.
> Laurent
>

-- 

Karlsruher Institut für Technologie (KIT)
Fakultät für Informatik
ATIS – Abteilung Technische Infrastruktur

Dipl.-Ing. Andreas Ladanyi
- Systemadministrator -

Am Fasanengarten 5, Gebäude 50.34, Raum 013
76131 Karlsruhe

Telefon: +49 721 608 - 4 3663
Fax: +49 721 608 - 4 6699
E-Mail: andreas.ladanyi@kit.edu
www.atis.informatik.kit.edu

www.kit.edu

KIT - Universität des Landes Baden-Württemberg und nationales Forschungszentrum in der Helmholtz-Gemeinschaft

Das KIT ist seit 2010 als familiengerechte Hochschule zertifiziert.