Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "EclipseSCADA/GettingStarted/DummySecurityConfiguration"
m |
m |
||
Line 9: | Line 9: | ||
* org.eclipse.scada.sec.authn.osgi.cfg.priority | * org.eclipse.scada.sec.authn.osgi.cfg.priority | ||
* org.eclipse.scada.sec.provider.script | * org.eclipse.scada.sec.provider.script | ||
+ | * org.eclipse.scada.ca.console | ||
And one of the following: | And one of the following: |
Revision as of 07:02, 2 December 2013
A dummy authorization scheme can be configured using the following recipe.
Ensure that the following bundles are started:
- org.eclipse.equinox.ds
- org.eclipse.scada.sec.osgi.manager
- org.eclipse.scada.sec.auth.logon
- org.eclipse.scada.sec.audit.log.slf4j
- org.eclipse.scada.sec.authn.osgi.cfg.priority
- org.eclipse.scada.sec.provider.script
- org.eclipse.scada.ca.console
And one of the following:
- org.eclipse.scada.ca.file
- org.eclipse.scada.ca.jdbc
Issue the following command on the OSGi console:
ca:create org.eclipse.scada.sec.osgi.manager allowAll serviceType=script priority=100000 "properties.script=true;"
This will create an authorization rule that will simply allow all actions.
The output should be something like this:
Completed - create - org.eclipse.scada.sec.osgi.manager/allowAll: [org.eclipse.scada.sec.osgi.manager/allowAll]={properties.script=true;, priority=100000, serviceType=script}
In addition you can check if the rule is active by issuing the following command:
secmgr:list
Which should show:
ID Priority ServiceType Realized TypeFilter IdFilter ActionFilter Error ====================================================================================== allowAll 100000 script X
Important is that the column "realized" is marked with an X.