D
dbeavon
Guest
It looks like the "OE Authentication Gateway" is probably the best approach for authenticating remote ABL database clients who need to connect to an OE database from PASOE. (Or I should say that if this is not the best approach then it is at least the latest approach.) I haven't heard too many discussions in the community about this, but maybe it is because it isn't widely used yet. Here is the guide for getting started. https://documentation.progress.com/output/OpenEdge117/pdfs/oeag/oeag.pdf The OpenEdge Database includes support for enhanced Client connection security beginning in the OpenEdge 11.6.2 release through a network of interdependent OpenEdge product security features. This enhanced database connection security puts the Database Administration (DBA) in control of which OpenEdge clients may establish and use those connections in order to access their server’s data I would still love to hear if someone can recommend alternative approaches. All we need is security that would allow certain remote PASOE servers to connect, while restricting other remote ABL connections (that are not production PASOE servers). I was hoping there might be something easier than the "oe auth gateway" that we could do in the short-term that would allow us to move ahead with PASOE, and then circle back later to implement the "oe auth gateway" at a later time. It would be nice to hear opinions about IP filtering. I'm wondering it that is a reasonable approach, or if it is too janky for OE database authorization.
Continue reading...
Continue reading...