I'm with you on that one. About 10 years ago, I spent a ridiculous amount of time getting SSO to work with EGL on WAS. On Apache, it's just another option in a drop-down list.
From: Mark Ford [mailto:Mark.Ford@xxxxxxxxxxx]
Sent: Friday, September 15, 2017 5:11 PM
To: IBMi Open Source Roundtable <opensource@xxxxxxxxxxxx>
Subject: Re: [IBMiOSS] node.js - 'module did not self-register' error
I don't think that's a dumb question and it's something we looked into doing in terms of using native OS APIs to interact with Kerberos to validate the information passed into the browser. We just couldn't find enough information about exactly which APIs we we needed to use to do this. There's not much in the way of examples in the IBM documentation. The APIs themselves seem well documented, just not how to use them from what I could see.
We did end up using the native approach for the second part of the problem - the mapping of the source ID to the target ID. We make use of the native EIM APIs to do the lookup and node just calls out into something we've written with the XML toolkit APIs.
If we can work out how to do the first part natively we will probably revisit and do similar.
One thing is for certain - we take a lot of what Apache does with SSO (with minimal configuration) for granted.
This thread ...
Re: [IBMiOSS] node.js - 'module did not self-register' error, (continued)
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact