# Single sign on with Spring/J2EE web apps?

**URL:** <https://forum.servoy.com/t/single-sign-on-with-spring-j2ee-web-apps/14093>\
**Category:** Classic Servoy\
**Created:** [June 3, 2011, 3:29pm UTC](https://forum.servoy.com/t/single-sign-on-with-spring-j2ee-web-apps/14093 "2011-06-03T15:29:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![guerry](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@guerry](https://forum.servoy.com/u/guerry)\
**Post date:** [June 3, 2011, 3:29pm UTC](https://forum.servoy.com/t/single-sign-on-with-spring-j2ee-web-apps/14093/1 "2011-06-03T15:29:34Z")

</div>

Hi all,

We have a Spring web app that we are thinking about integrating side-by-side with our Servoy web client app. Any pointers on the best way to approach single sign on in that case? Does Servoy use Spring security under the covers for the cookie/token? Or some other standard J2EE/Tomcat/whatever approach that we can hook into or also utilize to achieve SSO? In our Servoy web client app, we are using custom security with userids and passwords in a database table.

Thanks!

Guerry

---

<div class="post-metadata">

**Author:** ![guerry](https://avatars.discourse-cdn.com/v4/letter/g/f9ae1b/32.png) [@guerry](https://forum.servoy.com/u/guerry)\
**Post date:** [June 13, 2011, 5:45pm UTC](https://forum.servoy.com/t/single-sign-on-with-spring-j2ee-web-apps/14093/2 "2011-06-13T17:45:23Z")

</div>

Any answers to be had on this front? I’m beginning prototyping and will figure something out, but some direction would save a lot of time.

Thanks,

Guerry

---

<div class="post-metadata">

**Author:** ![jcompagner](https://yyz2.discourse-cdn.com/flex010/user_avatar/forum.servoy.com/jcompagner/32/4889_2.png) [@jcompagner](https://forum.servoy.com/u/jcompagner)\
**Post date:** [June 23, 2011, 11:17am UTC](https://forum.servoy.com/t/single-sign-on-with-spring-j2ee-web-apps/14093/3 "2011-06-23T11:17:27Z")

</div>

servoy doesnt use stuff like that, it has its own Session object (based on wicket) which holds the login information. This is not set into cookies.
