M
Michael Jacobs
Guest
Hello Peter, One of the reasons OpenEdge chose Spring Security was for its extensibility by both OpenEdge and customers. OpenEdge does redistribute and update certain Spring Security libraries and configurations for convenience to our customers who don't have to become experts. We do distribute some Spring Security libraries for other projects OpenEdge does not supply configurations for, but not all of them. But we don't limit enterprising individuals, like yourself, who create their own configurations or use any of the OpenEdge distributed libraries, so adding in the Spring Security OpenID project fits well. OpenEdge itself extends the core Spring Security by integrating it with the ABL application ( via a Client-Principal ) and in handling pure RESTful APIs. We'll maintain and support those extensions and you may freely use them in your own Spring Security configurations. I personally think redistributing your work would be great idea. Perhaps you can add in an Apache 2 open source license and post it on GitHub? We can also have an off-line conversation if you like and talk about redistributing your configuration with OpenEdge. One last note: starting in 11.7.0 the Spring Security configurations have been refactored for better maintainability and ease of use. I would expect someone who can configure their own OpenID support would have no problems doing an update. Please add a note to this forum with what you decide to do next. Mike Jacobs
Continue reading...
Continue reading...