Closed rstenet closed 3 years ago
The reason why this fails in LPS is because the Cred structure differs when enabling LPS or not. The current implementation only considers a sequence of commonName
, while we should be allowing for any X.509 OID within 2.5.4.X
. I'll give it a try shortly and get back, but this is a good catch! Thanks for reporting!
Can you git pull
and try it again now?
It seems to be properly fixed now:
$ pysapgenpse -c seclogin -dvf ~/sec/cred_v2 -x "Pa$$w0rd!"
pysapgenpse version: 0.1.20.dev0
pysapgenpse: Reading credentials file '/home/martin/sec/cred_v2'
0 (LPS:FALLBACK): /C=AR/CN=PSEOwner
(LPS:N/A): /home/martin/sec/test.pse
Credential cipher format version 2, algorithm AES256
PIN: 1234567890
1 readable SSO-Credentials available
Hi Martin, yes it is working now.
Hi,
if LPS is off or subject has only CN then it works.
Steps to reproduce the problem
1 Create pse and cred file
2 Create test script _readcred.py
3 Execute