Open SGE66 opened 2 years ago
Hello,
Could you provide me with a pkcs#11 log?
how to create one can be found here https://eid.belgium.be/en/technical-documentation#7480
Thank you
Hi Frederikus, could you please send me your mailing address? In the log, there's a lot of private information :-D
Hello Pieterjan,
Can you create a ticket at the service desk (please mention AZURE)? https://eid.belgium.be/en/contact
You may tell them that we agreed to escalate the ticket directly to the developers, I'll inform them as well. Then we can continue there.
Thank you, Frederik
On Fri, Sep 30, 2022 at 11:04 AM pieterjanvanneste @.***> wrote:
Hi Frederikus, could you please send me your mailing address? In the log, there's a lot of private information :-D
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1263310017, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJDUP5DTGGHI6RFFM3TWA2UJRANCNFSM6AAAAAAQR5S3GI . You are receiving this because you commented.Message ID: @.***>
Incident INC0663711
@Frederikus Can you give me an update on this?
Regards Pieterjan
Hello PieterJan,
Thank you for the logs, it looks similar to the former issue. Where the viewer gets a slot event and tries to handle it ,but in case of Hello For Business emulated card, during the handling errors are triggered which in turn seems to cause a new slot event. And then the viewer gets looping.
Normally the pkcs#11 should skip trying to communicate with unknown cars (that's what fixed the issue before), so currently looking into why this case is different.
Wkr, Frederik
Hi Frederik
Is there any update on this issue?
Regards
Pieterjan Vanneste Team Lead IT Operations T: +32 11 71 12 80 E: @.***
A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 13 okt. 2022 om 10:39 schreef Frederikus @.***>:
Hello PieterJan,
Thank you for the logs, it looks similar to the former issue. Where the viewer gets a slot event and tries to handle it ,but in case of Hello For Business emulated card, during the handling errors are triggered which in turn seems to cause a new slot event. And then the viewer gets looping.
Normally the pkcs#11 should skip trying to communicate with unknown cars (that's what fixed the issue before), so currently looking into why this case is different.
Wkr, Frederik
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1277249819, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFYZ2EML5MEDWXRCEJ6HEFTWC7DDBANCNFSM6AAAAAAQR5S3GI . You are receiving this because you commented.Message ID: @.***>
Hello PieterJan,
We're working on it and try to have it fixed in the next middleware release.
Wkr, Frederik
On Wed, Oct 19, 2022 at 9:03 AM pieterjanvanneste @.***> wrote:
Hi Frederik
Is there any update on this issue?
Regards
Pieterjan Vanneste Team Lead IT Operations T: +32 11 71 12 80 E: @.***
A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 13 okt. 2022 om 10:39 schreef Frederikus @.***>:
Hello PieterJan,
Thank you for the logs, it looks similar to the former issue. Where the viewer gets a slot event and tries to handle it ,but in case of Hello For Business emulated card, during the handling errors are triggered which in turn seems to cause a new slot event. And then the viewer gets looping.
Normally the pkcs#11 should skip trying to communicate with unknown cars (that's what fixed the issue before), so currently looking into why this case is different.
Wkr, Frederik
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1277249819, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AFYZ2EML5MEDWXRCEJ6HEFTWC7DDBANCNFSM6AAAAAAQR5S3GI
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1283529089, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJCP3TRNBMNM4CYL2Z3WD6MMFANCNFSM6AAAAAAQR5S3GI . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederikus
Is there any update on this issue? I think it is not fixed in the new release.
Regards
Pieterjan Vanneste Team Lead IT Operations T: +32 11 71 12 80 E: @.***
Hello Pieter-Jan,
No new version has been released yet. (5.1.8 dates from August 2022 https://eid.belgium.be/sites/default/files/software/RN518mw.pdf).
Wkr, Frederik
On Wed, Jan 18, 2023 at 12:27 PM pieterjanvanneste @.***> wrote:
Hi Frederikus
Is there any update on this issue? I think it is not fixed in the new release.
Regards
Pieterjan Vanneste Team Lead IT Operations T: +32 11 71 12 80 E: @.***
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1386902447, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJDFN2DUYCBXBRHBME3WS7HTBANCNFSM6AAAAAAQR5S3GI . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederikus
Is there any update on this issue?
Regards
Pieterjan Vanneste
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJHYGQQWF35BFCYDMKLYO2GLLAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTHA4DCMZRHA . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJHYGQQWF35BFCYDMKLYO2GLLAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJTHA4DCMZRHA>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCGGELIBSFWOXMJJO5TYPDFY7AVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJXHE2DKNRSGY . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCGGELIBSFWOXMJJO5TYPDFY7AVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJXHE2DKNRSGY>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJHQEHB7JQGDEWIPGRTYPZU7RAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUGA2DGOBWHE . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJHQEHB7JQGDEWIPGRTYPZU7RAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUGA2DGOBWHE>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCCUGUR225FD6BAY7ITYP3JGVAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUHAZTAMRWGM . You are receiving this because you commented.Message ID: @.***>
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCCUGUR225FD6BAY7ITYP3JGVAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBUHAZTAMRWGM>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB4JG7D457XWICNBX2XX7G3YP62KPAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGA2DMMRWGQ . You are receiving this because you authored the thread.Message ID: @.***>
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AB4JG7D457XWICNBX2XX7G3YP62KPAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGA2DMMRWGQ>
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCF7QSJJLPQWPXCSOQTYP7DBTAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGE4DGOJRGU . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCF7QSJJLPQWPXCSOQTYP7DBTAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBWGE4DGOJRGU>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJC5YOA6JZPI625Q5E3YRTRMTAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTG44DGMBRGE . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJC5YOA6JZPI625Q5E3YRTRMTAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRTG44DGMBRGE>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCCGTZUTW55O6AST7XLYRT5ETAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGA2DQNJTGU . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCCGTZUTW55O6AST7XLYRT5ETAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGA2DQNJTGU>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJBMOQU7ZAPLE2HFVCDYRT5ODAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGA2TEOJZGE . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJBMOQU7ZAPLE2HFVCDYRT5ODAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGA2TEOJZGE>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCHAIGC74JFDQCJXSQTYRT6VFAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGA3TCNBWGA . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCHAIGC74JFDQCJXSQTYRT6VFAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGA3TCNBWGA>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJB3EG7NVU4BIUXDQDDYSHM2PAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYHEZTSMZWGY . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJB3EG7NVU4BIUXDQDDYSHM2PAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYHEZTSMZWGY>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCEHQUF5OTJPKHVAJX3YSR655AVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGUZDANBVGM . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCEHQUF5OTJPKHVAJX3YSR655AVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGUZDANBVGM>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJGGVGV33BP7E6P7EPLYSSABLAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGUZTCMRXGU . You are receiving this because you were mentioned.Message ID: @.***>
with a new eidmw release soon
Point of curiosity as someone following this discussion from the outside: is the proposed fix in the new release supposed to address the general issue of "interference" from other smartcards present, or is it specific to WIndows Hello?
(Context: I ask because on my machine (macOS, totally different platform) the eID middleware typically fails to work when I have both my eID and YubiKey plugged in at the same time. If there's a chance that the root cause is the same and I potentially stand to benefit from this fix as well, I'm happy to try the new release and report back. If not, feel free to ignore this comment.)
Hello,
Thank you for your proposal, we'll let you know when a new macOS release is created. The proposed fix is related to all non-eID smartcards, so it could indeed also fix the issue you see (assuming the pkcs#11 library is being used).
Wkr, Frederik
On Fri, Feb 9, 2024 at 12:39 AM Matthias Valvekens @.***> wrote:
with a new eidmw release soon
Point of curiosity as someone following this discussion from the outside: is the proposed fix in the new release supposed to address the general issue of "interference" from other smartcards present, or is it specific to WIndows Hello?
(Context: I ask because on my machine (macOS, totally different platform) the eID middleware typically fails to work when I have both my eID and YubiKey plugged in at the same time. If there's a chance that the root cause is the same and I potentially stand to benefit from this fix as well, I'm happy to try the new release and report back. If not, feel free to ignore this comment.)
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1935100454, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJHPUSZG3OAEJXRZCXTYSVOZZAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGEYDANBVGQ . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJGGVGV33BP7E6P7EPLYSSABLAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZTGUZTCMRXGU>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCHQOSR6CQQC5WZIY23YSUCRTAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZUGU4TQOJYGA . You are receiving this because you commented.Message ID: @.***>
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCHQOSR6CQQC5WZIY23YSUCRTAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZUGU4TQOJYGA>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJBQLRRPBRGVTNPZN5LYTHATFAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYGE3DSOJYHE . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
Any status updates?
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 29 feb 2024 om 08:18 schreef Frederikus @.***>:
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJBQLRRPBRGVTNPZN5LYTHATFAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZYGE3DSOJYHE>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1970546913, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCDMTQBMBPGJ557MJ6TYV3K5LAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGU2DMOJRGM . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
Yes, we found a workaround for the above unwanted behavior of non-eid cards which we are currently testing.
On Mon, May 6, 2024 at 11:24 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Any status updates?
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 29 feb 2024 om 08:18 schreef Frederikus @.***>:
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1970546913, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCDMTQBMBPGJ557MJ6TYV3K5LAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGU2DMOJRGM>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2095542531, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJHWBJBG6QRV4RJ2WU3ZA5D3XAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGU2DENJTGE . You are receiving this because you were mentioned.Message ID: @.***>
We created a new test release that addresses the issue of reading non-eID cards, it can be found here: https://dist.eid.belgium.be/releases/5.1.19/
On Sat, May 11, 2024 at 10:07 AM Frederik Vernelen < @.***> wrote:
Hello Sacha,
Yes, we found a workaround for the above unwanted behavior of non-eid cards which we are currently testing.
On Mon, May 6, 2024 at 11:24 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Any status updates?
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 29 feb 2024 om 08:18 schreef Frederikus @.***>:
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1970546913, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCDMTQBMBPGJ557MJ6TYV3K5LAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNZQGU2DMOJRGM>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2095542531, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJHWBJBG6QRV4RJ2WU3ZA5D3XAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGU2DENJTGE . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
The test version for the issue with non-eID card does not work for our issue. It's still the same issue. ERROR: Cannot read Carddata: Open slot failed [image: image.png]
Any update on a new version that also affects eID cards? This problem dates back from 2022, we're in need of a solution.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 20 mei 2024 om 18:00 schreef Frederikus @.***>:
We created a new test release that addresses the issue of reading non-eID cards, it can be found here: https://dist.eid.belgium.be/releases/5.1.19/
On Sat, May 11, 2024 at 10:07 AM Frederik Vernelen < @.***> wrote:
Hello Sacha,
Yes, we found a workaround for the above unwanted behavior of non-eid cards which we are currently testing.
On Mon, May 6, 2024 at 11:24 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Any status updates?
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 29 feb 2024 om 08:18 schreef Frederikus @.***>:
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-1970546913,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2095542531, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJHWBJBG6QRV4RJ2WU3ZA5D3XAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJVGU2DENJTGE>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2120744539, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCA6CBTQZ6JIFTCQLBDZDIMZ3AVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQG42DINJTHE . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
Thanks for testing. Could you provide us with a detailed pkcs#11 log (through servicedesk)?
What do you mean with "a new version that also affects eID cards" ? The issue we are looking into here is that some non-eid cards (like the simulate cards from Hello for business) respond with errors when being talked to through our pkcs#11. And that applications that do not handle those errors (e.g. by skipping those cards like the eID Viewer on Windows does), seem to just stop when encountering them. We have been testing with several non-eid cards, and noticed they are filtered out now. In order to get some more info why the ones you are encountering are still getting through, some logs would really be helpful.
Wkr, Frederik
On Tue, May 21, 2024 at 9:56 AM SachaPhilipsen @.***> wrote:
Hi Frederik
The test version for the issue with non-eID card does not work for our issue. It's still the same issue. ERROR: Cannot read Carddata: Open slot failed [image: image.png]
Any update on a new version that also affects eID cards? This problem dates back from 2022, we're in need of a solution.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 20 mei 2024 om 18:00 schreef Frederikus @.***>:
We created a new test release that addresses the issue of reading non-eID cards, it can be found here: https://dist.eid.belgium.be/releases/5.1.19/
On Sat, May 11, 2024 at 10:07 AM Frederik Vernelen < @.***> wrote:
Hello Sacha,
Yes, we found a workaround for the above unwanted behavior of non-eid cards which we are currently testing.
On Mon, May 6, 2024 at 11:24 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Any status updates?
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 29 feb 2024 om 08:18 schreef Frederikus @.***>:
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1970546913>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2095542531,
or unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2120744539, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCA6CBTQZ6JIFTCQLBDZDIMZ3AVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQG42DINJTHE>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2121993120, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJADV5FR43Q7FD2FUKTZDL43TAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRHE4TGMJSGA . You are receiving this because you were mentioned.Message ID: @.***>
Hi Frederik
It appears we are back to square one then. If you read back this thread from around october 2022 it was clearly mentioned by my colleague Pieterjan that there was an issue regarding eID and Azure joined end-devices. Now we're talking about a release created for non-eID cards. Is there any update on the eID-middleware software for Azure joined devices? It's no longer possible to use eID with those devices. More and more companies are migrating to Azure joined devices, making the option eID unusable.
It's always the same error, the one mentioned a couple of times in this thread: ERROR: Cannot read Carddata: Open slot failed
What is the email address for the servicedesk? Or could you forward this to the service desk please?. Both options are fine. We're just looking for a solution or at the very least a workaround for our customers and ourselves.
Thanks in advance.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 23 mei 2024 om 14:09 schreef Frederikus @.***>:
Hello Sacha,
Thanks for testing. Could you provide us with a detailed pkcs#11 log (through servicedesk)?
What do you mean with "a new version that also affects eID cards" ? The issue we are looking into here is that some non-eid cards (like the simulate cards from Hello for business) respond with errors when being talked to through our pkcs#11. And that applications that do not handle those errors (e.g. by skipping those cards like the eID Viewer on Windows does), seem to just stop when encountering them. We have been testing with several non-eid cards, and noticed they are filtered out now. In order to get some more info why the ones you are encountering are still getting through, some logs would really be helpful.
Wkr, Frederik
On Tue, May 21, 2024 at 9:56 AM SachaPhilipsen @.***> wrote:
Hi Frederik
The test version for the issue with non-eID card does not work for our issue. It's still the same issue. ERROR: Cannot read Carddata: Open slot failed [image: image.png]
Any update on a new version that also affects eID cards? This problem dates back from 2022, we're in need of a solution.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 20 mei 2024 om 18:00 schreef Frederikus @.***>:
We created a new test release that addresses the issue of reading non-eID cards, it can be found here: https://dist.eid.belgium.be/releases/5.1.19/
On Sat, May 11, 2024 at 10:07 AM Frederik Vernelen < @.***> wrote:
Hello Sacha,
Yes, we found a workaround for the above unwanted behavior of non-eid cards which we are currently testing.
On Mon, May 6, 2024 at 11:24 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Any status updates?
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 29 feb 2024 om 08:18 schreef Frederikus @.***>:
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1970546913>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-2095542531>,
or unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2120744539,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2121993120, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AA4FYJADV5FR43Q7FD2FUKTZDL43TAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRRHE4TGMJSGA>
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2126950144, or unsubscribe https://github.com/notifications/unsubscribe-auth/BFMNZCDZJJZI5TIUM3G7AZ3ZDXL7ZAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWHE2TAMJUGQ . You are receiving this because you commented.Message ID: @.***>
Hello Sacha,
That initial thread, and the following pkcs#11 logs was indeed the one I had in mind. It mentioned that when using Azure devices, multiple slots are detected, but when reading the slot with the Hello For Business emulated card, an error appeared: " ERROR: Cannot read Carddata: Open slot failed" We do not have Azure devices, so we tried to reproduce this situation with non-eID cards. (just like the Hello For Business emulated card is a non-eID card). Some non-eID cards we tested with gave the same results as what was reported here, so we made changes to the pkcs#11 testing against those cards. "Open slot failed" is a rather high level error, and a pkcs#11 log would provide us more detail on why the slot with the "the Hello For Business emulated card" is still appearing.
At the same time, we noticed that the eID Viewer does not run into this issue (as it skips slots it cannot handle), hence why we think that any solution that receives this error might also be able to work around it.
email address of the service desk is: https://eid.belgium.be/en/contact They are aware of this thread, but if you create a ticket with them mentioning this thread; you'll have a private channel in case you want to send over some logs.
Wkr, Frederik
On Fri, May 24, 2024 at 1:24 PM SachaPhilipsen @.***> wrote:
Hi Frederik
It appears we are back to square one then. If you read back this thread from around october 2022 it was clearly mentioned by my colleague Pieterjan that there was an issue regarding eID and Azure joined end-devices. Now we're talking about a release created for non-eID cards. Is there any update on the eID-middleware software for Azure joined devices? It's no longer possible to use eID with those devices. More and more companies are migrating to Azure joined devices, making the option eID unusable.
It's always the same error, the one mentioned a couple of times in this thread: ERROR: Cannot read Carddata: Open slot failed
What is the email address for the servicedesk? Or could you forward this to the service desk please?. Both options are fine. We're just looking for a solution or at the very least a workaround for our customers and ourselves.
Thanks in advance.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op do 23 mei 2024 om 14:09 schreef Frederikus @.***>:
Hello Sacha,
Thanks for testing. Could you provide us with a detailed pkcs#11 log (through servicedesk)?
What do you mean with "a new version that also affects eID cards" ? The issue we are looking into here is that some non-eid cards (like the simulate cards from Hello for business) respond with errors when being talked to through our pkcs#11. And that applications that do not handle those errors (e.g. by skipping those cards like the eID Viewer on Windows does), seem to just stop when encountering them. We have been testing with several non-eid cards, and noticed they are filtered out now. In order to get some more info why the ones you are encountering are still getting through, some logs would really be helpful.
Wkr, Frederik
On Tue, May 21, 2024 at 9:56 AM SachaPhilipsen @.***> wrote:
Hi Frederik
The test version for the issue with non-eID card does not work for our issue. It's still the same issue. ERROR: Cannot read Carddata: Open slot failed [image: image.png]
Any update on a new version that also affects eID cards? This problem dates back from 2022, we're in need of a solution.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr https://www.linkedin.com/company/prato
Op ma 20 mei 2024 om 18:00 schreef Frederikus @.***>:
We created a new test release that addresses the issue of reading non-eID cards, it can be found here: https://dist.eid.belgium.be/releases/5.1.19/
On Sat, May 11, 2024 at 10:07 AM Frederik Vernelen < @.***> wrote:
Hello Sacha,
Yes, we found a workaround for the above unwanted behavior of non-eid cards which we are currently testing.
On Mon, May 6, 2024 at 11:24 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Any status updates?
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 29 feb 2024 om 08:18 schreef Frederikus @.***>:
Small status update from our side.
When creating the new release, we did more tests with non-eID cards and noticed some behavior we did not expect. We are currently looking into this and want to correct it before creating the release.
Wkr, Frederik
On Mon, Feb 12, 2024 at 8:33 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Sure thing, we will test it once the new version is made available. Just let me know when. Thanks!
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/ https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 18:21 schreef Frederikus @.***>:
Hello Sacha,
Thank you for the error description.
We discussed this today and plan to come with a new eidmw release soon. Would you, or anyone of the team be available for testing with that release (we do not have a Hello for business setup), and if needed provide logs and info (through the service desk)?
Wkr, Frederik
On Thu, Feb 8, 2024 at 8:53 AM SachaPhilipsen @.***> wrote:
Hi Frederik
It's the same error: "( ERROR: Cannot read Carddata: Open slot failed )"
Thanks for looking into this.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ https://www.facebook.com/PratoHR/
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 8 feb 2024 om 08:44 schreef Frederikus @.***>:
Hello Sacha,
Thank you for testing. Your image didn't come through, but I'll check with the service desk this afternoon if we can follow up through the original ticket.
The base issue being that Windows Hello creates virtual readers and cards, which are (of course) detected by the pkcs#11 module and presented to the layers above. If the layers above start communicating with these virtual cards they will not receive what they might expect. To make it easier for the applications above, we try to filter out those virtual cards already in the pkcs#11 layer as soon as possible. With the eID Viewer this seems to work, but the eID Viewer itself also has some logic to handle/ignore unknown cards.
Wkr, Frederik
On Tue, Feb 6, 2024 at 8:39 AM SachaPhilipsen @.***> wrote:
Hi Frederik
Again, the same error appears: [image: image.png]
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 16:10 schreef Frederikus @.***>:
Hello Sacha,
Apologies for the confusion. Pieterjan tested it with a 2022 version of the pkcs#11, we made (based upon his logs) relevant changes in the pkcs#11 in the meantime. These changes are also part of the eID Viewer.. You told me the eID Viewer currently works fine, which is why I'm asking if it is possible to test the Betrust plugin with the pkcs#11 that comes with that eID Viewer.
Wkr, Frederik
On Fri, Feb 2, 2024 at 3:59 PM SachaPhilipsen @.***> wrote:
Hi Frederik
As Stefan commented before, my colleague Pieterjan has already tested it with the PKCS#11. Same thing for me. It's becoming a bit of an issue now where we get sent back and forth. If there are any other options to try, please let me know and provide us with the necessary documentation.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op vr 2 feb 2024 om 15:57 schreef Frederikus @.***>:
Hello Sacha,
Were you, or anyone from Betrust, able to perform the suggested test?
Wkr, Frederik
On Fri, Feb 2, 2024 at 2:16 PM SachaPhilipsen @.***> wrote:
Hi Frederik
Is there any feedback regarding this issue yet? It's been 2 years already.
KR Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op di 23 jan 2024 om 15:35 schreef SGE66 @.***>:
Hi All,
I'm Stefan from Betrust. In the past Pieterjan has done the necessary testing with the pkcs#11 library and given the results back to FedICT.
Stefan
On Tue, 23 Jan 2024 at 14:20, SachaPhilipsen @.***> wrote:
Hi Frederikus
Our company is a user of the Betrust plugin. Our software makes use of the plugin to subscribe temporary workers (interim) through the use of eID instead of doing everything manually.
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op ma 22 jan 2024 om 22:15 schreef Frederikus @.***>:
Hello Sacha,
Thank you for your feedback. Just for my understanding, are you a user or a developer of the betrust plugin? In case you are a developer, could you try a build that uses the pkcs#11 library that is installed with the eID Viewer?
Wkr, Frederik
On Mon, Jan 22, 2024 at 2:49 PM SachaPhilipsen @.***> wrote:
Hi Frederik
The eID Viewer reads and displays my information correctly. Using the BeTrust plugin I receive the known error: "( ERROR: Cannot read Carddata: Open slot failed )"
Kind regards Sacha Philipsen Team Lead IT Operations T: +32 11 71 12 80 E: @.*** A: Corda Campus - Corda 6 Kempische Steenweg 293/35 3500 Hasselt http://www.prato.be/ < https://www.facebook.com/PratoHR/>
https://twitter.com/pratohr < https://www.linkedin.com/company/prato>
Op do 18 jan 2024 om 08:32 schreef Frederikus @.***>:
Hello Sacha,
In order to determine if the changes in the pkcs#11 for the eID Viewer fixes this issue, can you test with the pkcs#11 library that comes with the eID Viewer? After installing the eID Viewer (separate install from the middleware), you can find this one at e.g. C:\Program Files (x86)\Belgium Identity Card\EidViewer
Wkr, Frederik
On Tue, Jan 16, 2024 at 3:39 PM SachaPhilipsen @.***> wrote:
Hi Frederikus
We're still awaiting feedback. Could you please provide us with the most recent status?
Kind regards
Sacha
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1893881318>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1897945626>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904043869>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1904830263>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906046264>,
or
unsubscribe <
. You are receiving this because you authored the thread.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1906183915>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1923783011>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924048535>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924052991>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1924071460>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1928939366>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933520453>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1933531275>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub <
https://github.com/Fedict/eid-mw/issues/180#issuecomment-1934598980>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1938169989>,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-1970546913>,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub < https://github.com/Fedict/eid-mw/issues/180#issuecomment-2095542531>,
or unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2120744539,
or
unsubscribe <
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2121993120,
or
unsubscribe <
. You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2126950144, or unsubscribe < https://github.com/notifications/unsubscribe-auth/BFMNZCDZJJZI5TIUM3G7AZ3ZDXL7ZAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRWHE2TAMJUGQ>
. You are receiving this because you commented.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/Fedict/eid-mw/issues/180#issuecomment-2129293034, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA4FYJCIV4VCBLCQGRXLVJLZD4PQTAVCNFSM6AAAAAAQR5S3GKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRZGI4TGMBTGQ . You are receiving this because you were mentioned.Message ID: @.***>
Hi,
I refer to https://github.com/Fedict/eid-mw/issues/100
We have this issue if Windows Hello is used connecting to an Azure account ('local' logon with PIN code is no problem).
We can pinpoint the problem to following code (code used from sdk40 (example data.c file):
retVal = (pFunctions->C_GetSlotList) (CK_TRUE, 0, &slot_count);
Appareantly (card) reader cannot be accessed, no 'slots' are found.
Anyone experiencing the same problem and any idea to solve this ?
Tested with latest middleware version 5.0.17 (but alo 4.4.4 gave same error).
` CK_ULONG beidsdk_GetData() { void *pkcs11Handle; //handle to the pkcs11 library
CK_FUNCTION_LIST_PTR pFunctions; //list of the pkcs11 function pointers CK_C_GetFunctionList pC_GetFunctionList; CK_RV retVal = CKR_OK; DWORD err;
...`