|
[x]
Posted via EE Mobile
|
|
| Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again. |
|
|
|
|
|
[x]
The Solution Rating System
|
|
| With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating. - The Grade of the Solution
- The Zone Rank of the Expert Providing the Solution
- The Number of Author and Expert Comments
- The Number of Experts Contributing
- The Feedback of the Community
Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site. If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support. Thank you! |
|
|
|
|
Asked by intlgd in Spring, J2EE, Java Server Pages (JSP)
Hello all,
I have a basic understanding of how spring security works from the Spring in Action 2 book, but my situation is a little unique. So let me explain:
We have apache sitting in front of port 80 (on a secured intranet) and authenticate through a proprietary apache module there. This generates an encrypted cookie and stores it so that I can access it from my application. My current authentication method uses a Struts2 action and calls the database to see if the user exists. If he doesn't we automatically create a user in our system with ROLE_BASIC privileges.
What I want to do is tie in spring security so I can secure certain parts of my web application from users typing in the URL. We have roles set up so we're trying to make it roles based access. I was hoping to do this through a configuration instead of littering my JSPs with this stuff.
From what I can tell everything in the Spring In Action 2 example would work except that I am not asking the user to log into a page and I'm also not expecting them to necessarily already have an account.
Any thoughts on how I could use what Spring (Acegi) has, but role in my own unique requirements.
Thanks,
Jared
20091111-EE-VQP-89 - Hierarchy / EE_QW_3_20080625
