I have a jetty server running some ssh (spring-struts2-hibernate) modules. It's typically config by a web.xml file. Now I want all new module to use spring-webflux techique with functional endpoints. All ssh modules must keep running. How to mix the new webflux module to this jetty server?
Related
I am trying to upgrade my existing grails application from version 2.5.6 to 3.3.11.
So far, container managed application was configured in the application via web.xml, with <login-config>. Here is the configuration:
<login-config>
<auth-method>FORM</auth-method>
<form-login-config>
<form-login-page>/login/login</form-login-page>
<form-error-page>/login/login_error</form-error-page>
</form-login-config>
</login-config>
As grails 3 has stopped supporting web.xml file, I am wondering how to maintain Container Managed Authentication. The reason for using Container Managed Authentication (CMA) is that our application doesn't want to handle the authentication process, as different customers have different authentication mechanisms at their end. So we prefer CMA.
Have read many online forums, they all end up with Spring Security plugin. But didn't find a configuration with Spring Security which gives control of authentication to the container.
So, how to configure CMA with Grails 3?
You could use Apache with Jenkins to use client certificates for authentication, but is there a less bulky way that is just as simple on Windows or RHEL? Perhaps, customizing the Jenkins code is an option, since it says it already runs in a Jetty servlet? A way to do this in Hudson itself?
With Apache Web Server, I was fighting with some plugins, like Selenium related plugins. Also, I noticed more issues connecting to slaves when using a proxy despite using the tunnel option. Leaner and meaner would be nice.
I have a set of dockerized microservices (spring boot with jersey application) deployed on EC2 instances. Each service exposes rest apis which i need to create a spec for.
As a first step, i have included swagger-core in all the spring boot apps which generates a .json/.yaml file and serves it on http as a rest resource when the service is up.
I want to use slate to serve the api specification for all the services as a single resource (aggregated from individual json/yaml files) over http/s.
Slate (https://github.com/lord/slate) uses markdown format to serve the static content.
Library Swagger2Markup can be used to generate the markdown file by aggregating the api specs (json/yaml files) from each services (each have their own json/yaml file generated).
Using this markdown file, i can use slate default middleman to build the static content and serve it over http.
Question: what can be considered a best practice for seamlessly integrating this process to the jenkins build.
I have a spring boot 1.2 web application is deployed on standalone tomcat.
I need to authorize an url based on remote IP.
In case of embedded tomcat , we can use
server.tomcat.remote_ip_header= x-forwarded-for
How do we configure, when deployed in standalone tomcat.
Note :
I did try RemoteIpValve of tomcat by setting remoteIpHeader="x-forwarded-for" and it did not work and My tomcat is behind a web Application firewall.
without changing tomcat settings etc, can we tell spring security to look for remote ip in x-forwarded-for(in stand alone tomcat deployement)
You can use Remote IP Filter available with Tomcat. There are many such filters available.
Please see (Tomcat Documentation](http://tomcat.apache.org/tomcat-7.0-doc/config/filter.html#Remote_IP_Filter)
You can configure these filters in $CATALINA_BASE/conf/web.xml which will be available for all web application or you can do it in web applications web.xml.
I have a simple Grails app that I've written to authenticate against an LDAP server. To develop it, I've installed ApacheDS locally and populated it with an LDIF file. Now I want to deploy it to CloudBees. Is it possible to install an LDAP server on CloudBees?
If not, an alternative seems to be to use the Grails ldap-server plugin. However, it doesn't have any documentation on how to configure it. How do I configure this plugin to load an LDIF on startup?
Unfortunately, running LDAP in a CloudBees app container/stack won't work because in-bound routing to your application port must be over HTTP/HTTPS.
Alternative 1: host the LDAP server outside of CloudBees (like on your own EC2 server)
Alternative 2: [for the highly motivated] you might be able to get a WebSocket gateway of some kind to work, but you'd special code on the client and server side to negotiate the socket stream hand-off outside of the LDAP server and client. [Client -> WS-Client --> CloudBees --> WS-Server --> LDAP Server]
gripe: why can't all protocols support virtual hosting like HTTP? -- that would make them much more Cloud-friendly :(