[ http://thecla.homeftp.net:8380/jira/browse/BPM-107?page=history ]
Wouter Zoons updated BPM-107:
-----------------------------
Description:
In the current version of the cartridge it is not possible to use security and
still allow for some use cases to be "unsecured" (meaning allowing an anonymous
user to have acces to this use case).
On the mailinglist there was some discussion on how to deal with this and I
agree defining a new stereotype lyke "Secured" and "Unsecured" is a good way to
deal with this. For my understanding this would mean that:
- A use case that is typed "Unsecured" with no associations with any actors is
accessible for anyone.
- A use case that is types "Unsecured" with several associations with actors is
accessible for anyone.
- A use case that is typed "Secured" with no associations with any actors is
NOT accessible by anyone.
- A user case that is typed "Secured" with several associations with actors is
ONLY accessible for those actors/roles.
was:
In the current version of the cartridge it is not possible to use security and
still allow for some use cases to be "unsecured" (meaning allowing an anonymous
user to have acces to this use case).
On the mailinglist there was some discussion on how to deal with this and I
agree defining a new stereotype lyke "Secured" and "Unsecured" is a good way to
deal with this. For my understanding this would mean that:
- A use case that is typed "Unsecured" with no associations with any actors is
accessible for anyone.
- A use case that is types "Unsecured" with several associations with actors is
accessible for anyone.
- A use case that is typed "Secured" with no associations with any actors is
NOT accessible by anyone.
- A user case that is typed "Secured" with several associations with actors is
ONLY accessible for those actors/roles.
Environment:
Version: 3.0 M3
Fix Version: 3.0 RC2
Erwin, could you comment on this issue ? I feel like closing it otherwise :-)
Do you think there would be an alternative way, like stereotyping the actor or
maybe even something completely different ? I personally don't like to use
stereotypes too much.
thanks
> No possibilit to allow anonymous user access to a use case (when security
> setting is on)
> ----------------------------------------------------------------------------------------
>
> Key: BPM-107
> URL: http://thecla.homeftp.net:8380/jira/browse/BPM-107
> Project: Bpm4Struts Cartridge
> Type: Bug
> Versions: 3.0 M3
> Reporter: Erwin Teseling
> Assignee: Wouter Zoons
> Fix For: 3.0 RC2
>
>
> In the current version of the cartridge it is not possible to use security
> and still allow for some use cases to be "unsecured" (meaning allowing an
> anonymous user to have acces to this use case).
> On the mailinglist there was some discussion on how to deal with this and I
> agree defining a new stereotype lyke "Secured" and "Unsecured" is a good way
> to deal with this. For my understanding this would mean that:
> - A use case that is typed "Unsecured" with no associations with any actors
> is accessible for anyone.
> - A use case that is types "Unsecured" with several associations with actors
> is accessible for anyone.
> - A use case that is typed "Secured" with no associations with any actors is
> NOT accessible by anyone.
> - A user case that is typed "Secured" with several associations with actors
> is ONLY accessible for those actors/roles.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://thecla.homeftp.net:8380/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Andromda-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/andromda-devel
