aspose file tools*
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes Login component Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Spring in Action this week in the Spring forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "Login component" Watch "Login component" New topic
Author

Login component

Ashish Sarin
author
Ranch Hand

Joined: Nov 20, 2000
Posts: 432
    
    5
Hi,

Do we need to show a login component even when using JAAS ?

thanks
Ashish


Author of
Getting started with Spring Framework
Portlets in Action
Spring Roo 1.1 Cookbook
Portlets blogSpring Roo blog
J Gupta
Ranch Hand

Joined: Jul 16, 2008
Posts: 30
What/who is your authentication provider. You might want to wrap for example LDAP authentication or OS authentication in Login component
Deepak Bala
Bartender

Joined: Feb 24, 2006
Posts: 6662
    
    5

Originally posted by Ashish Sarin:
Hi,

Do we need to show a login component even when using JAAS ?

thanks
Ashish


Well your solution should mention that you are using JAAS somewhere. If you do not choose to show login details in sequence or component diagrams, you should at least mention these details in the documentation (which I would not recommend).

A short answer would be - yes.


SCJP 6 articles - SCJP 5/6 mock exams - More SCJP Mocks
Ashish Sarin
author
Ranch Hand

Joined: Nov 20, 2000
Posts: 432
    
    5
Showing the login component in Component diagram is fine but which component I will show to be dependent upon the login component when using JAAS ?
John Summers
Ranch Hand

Joined: Oct 06, 2003
Posts: 125
Is this whole forum full of people hysterically over-reacting to the assignment requirements?

What is with 'solution documentation'? You don't need any. It says in black and white what you need to submit:
-a single class diagram
-a single component diagram
-a sequence/activity diagram for each use case
-a list of assumptions
-an index.html with links to the above.

what is with people including all this other stuff? Authentication documentation? Database schemas? I have seen other people talking about preparing these whole documents to go with the solution.

I have put one single example of re-directing to the 'create profile' and 'log in' use cases on my sequence diagrams. I have not supplied those use cases, it is not in the requirements. This is a J2EE app. You dont need to riddle your code or diagrams with authentication stuff.

j
Deepak Bala
Bartender

Joined: Feb 24, 2006
Posts: 6662
    
    5

what is with people including all this other stuff? Authentication documentation? Database schemas? I have seen other people talking about preparing these whole documents to go with the solution.


Thats not a bad thing. Documenting assumptions with the solution can add clarity. It is up to the candidate to decide what info needs to be added to represent a complete solution.

I have put one single example of re-directing to the 'create profile' and 'log in' use cases on my sequence diagrams. I have not supplied those use cases, it is not in the requirements. This is a J2EE app. You dont need to riddle your code or diagrams with authentication stuff.


That should suffice as long as you feel the reviewer can understand your design. Good luck
John Summers
Ranch Hand

Joined: Oct 06, 2003
Posts: 125
Thanks for your measured reply John.

Sorry I kind of went off on on with my original post. I do actually think that a lot of people in this forum go way, WAY too far with their submission and go totally over the top. I always thought the whole point was that your design should be obvious from your diagrams, and if it's not then change the diagrams!

there again... i haven't submitted yet.
jj
 
 
subject: Login component