Tommy2d

Results 22 comments of Tommy2d

The type errors are caused by $element never being set (as part of the deserialization / serialization routine). Yes, I am using tag v4.6.0 (46d93daa9a96a1d896fe35cb75897a91e1795442). This is the stack trace:...

The problem is 100% reproducible for me when authenticating against ToegangsVerleningsService(TVS), and it seems to happen as part of the Unserialization of ActingSubjectID.

I can confirm that the test case works for me.

It doesn't change a thing I'm afraid. Same error, even after cleaning the sqlite db.

The serialized attributeValue is stored in sqlite (SimpleSAMLphp_kvstore) right? none-working (stock) version: `a:1:{i:0;O:29:"SAML2\XML\saml\AttributeValue":1:{i:0;s:2716:"/ser96syVNo+mPtHCvYg2oqs7cPgGzczehq8+DQB08gy19RjCEat6YCRSDrilpcRw+lgqyEcr1zJKeU0i84tlGrUdfJ5uWND5H9+FQclLWD36BBtJ4GfsyzSADFfKcu4R6MubZpTxAdDApTopAt8+ZAy9PV9QVWvDZntfzTlise2v9pnTs1xWHmBAO1AmsIoZyFwaoZQUgJrsp2gyuXRTbM4dL96naxj3T0vpPsCUHbNUx1Vw7JFuEZn/JW98gab429w4zM+OY6rPdwwSfAyLq+zGFbxOd33ZihlQHSGLQU=_b420654655d491b49555c698f80efb7bda3ac6efxcF7/aS3RW0yGEiG1mfDSAmqhwLWpWC8msGp2vlaHsXHpBrDbQb4NYE7AQ/t9cRbDDvmsZmwIZe2B7oMUPz1jhHymmQqJ7WTJOBc7V04zbA/cuzgkxa0gSIPoTHkrRhF7bEvDkkTTZn+X+U2QdSFZc+AB8dIvc83hc0hvgtE1hQUlAzgnw3FO0lnQuVTDI57j9mJqyjfHaN3BqusSqmwuOcZsN+cx9fbWsyFznRlUxoK9Sj5Sn0xuc3Qg5IBjDWTB8y8Ab+vLp3DlNjGfEQIpg9mzbKaMf2fN4Dx7GUya7tdOR5XBkLmu58+opsKb73t5OgjBEdo4q+ETW8fe9w4nRhFD6skRSFA5XyIc0iF3YsJkCfxbUt9BefjwuKAbg8T4FBxyao7kQckfl6k5+wcyX6RQ6wK23orrihgNQCfvvSzmsivtArpXwB7kg4M/H1DUeZYLjh3xrVPZ37wrcwc9fnudKUgzkWjTAc8/si6PqL4LWb35Qk3LqwkdX+dy4qYSvawOa9eqjtalAJYFjYbhAb4csQUm10KFnFNTy2SJRXkf6If2k38UfFJok0cN2RTpaSrn1O1U0BMmhLh3K/bdSmWT6lVGgr7OXdhLfADAqu7BORI/gpFMsDhs41ul0i1vv6hBa0ng/1B2BR4qo1yCaerYV0u0+oF0K5nd5xxFI0=";}}` v.s. (working, with the serialization/deserilization functiones removed in AttributeValue): `a:1:{i:0;C:29:"SAML2\XML\saml\AttributeValue":2726:{s:2716:"vErnRkA0oSmtQGamjZGa9RFN25SUx1UVLsLAOtopt7pyywTD7wu9pyocfD4HqduXCsvaiZpJykz11utZdvtJ0sOdm9oE+lAtNTUnKzGSNoSopGCzwNu5pqwhIEvWEWeilmJayAC2elpRYOnUs/rePxibz0Wbqa7BItLt6ZkKTtMkv0U0PpgGenF1pWzsahRtw6Y5tFq7xFQkG/z0Lz5rJ+IxExYXgB3LN6FBmVcB1ioahk2ovOwbLQ+lNAdqUMhpZx6fgdL2v7g4OYPK0rDgSALU3gU3dvU4hC/Kk9N5Rkw=_b420654655d491b49555c698f80efb7bda3ac6efd5X+psMTEy9DWDoVotB5sPHdNpofv5BdPUleflhGfjbjGIfWbV9fK+jMkQ4cqwSWwmTGSQ8OO+lYA9IwZasnWygAu3dSSlYd+sd/m2waz83MrTBsTtZUzwy8N18tNMu4xB/tb45XPvis9agg6b2RdpDSS1m5BKK+MMKgX2ZYIqOW6cbXxl73YJHHHpcTi1TsI+tx6DLNWB2ku5wpS3cFB3c0Tws9qG+YBwTzfp1gFhzvBQDNxLWVjPKEWEw5Do1dp8f7jOPWq0sscz6DaTJH3RStwOSLF2vsayGZUgqNXyPHX12dFNGHiTXEWVYcuXsqG8sXJQyUmE5kYqN/D8NT1BIq50L6xIKkQGxNSlyAAkvkV87b1z6X2Fvk6Hvmx+eqauJX/BKknqgNZL/I5xfysDcNG5i0vA/kOVai4LvmdEoUSq1dIWcGsiW5pbM13R+DddkUegGcZctmFLcafBM2A3WztGclLWSJea+hh24YurcRGQVoOaZcYRmGVA0cYRQjfcSb3mvGxl01I9f27Hzv6/pXMWmEetpNhO4Pxy4GIwatJ7clW+s679f6N4+qepzbnxqjMLOmRPilJ0t9+wHYQ9wc2+NN4lssLNNz852rb5Rs9HDTvOyvtV7ew4HdMqGjXeJt545pQzSonuzCVVs67Nuhi/rmOktsav8tP0N8izE=";}}` The first difference that I notice is...

I'm indeed using sqlite for session storage. But this is only to make it easier to access the serialized data: the issue exists on all session storage providers. Let me...

Interesting. I just mirrored the branch onto our gitlab environment so I will be able to test. Keep me posted in case I need to perform additional tests using this...

Any updates on this issue @tvdijen? Is there anything I can do to assist here?

We're using the yubikey's PIV interface for many different things, including VPN and SSH, so I cannot easily skip using the PCKCS11 provider. Without any further configuration, it simply uses...

I just reproduced this issue using my own compilation of the app. It provides additional information: ``` 2020-06-24 16:02:55.378338+0200 ssh[11508:562356] [pcscapi] communication with ctkpcscd failed debug1: provider /Library/OpenSC/lib/pkcs11/opensc-pkcs11.so: manufacturerID cryptokiVersion...