EclipseSCADA/GettingStarted/CARecipes

{Note|Bundles required|All configuration objects require factories provided by bundles. Ensure that the require bundles are also started}}

CA Main Bundles

All recipes require the following bundles to be started:

   org.eclipse.equinox.ds
   org.eclipse.scada.ca.console
   org.eclipse.equinox.console
   org.apache.felix.gogo.runtime
   org.apache.felix.gogo.shell
   org.apache.felix.gogo.command

And one of the following:

   org.eclipse.scada.ca.file
   org.eclipse.scada.ca.jdbc 

Dummy authentication

A dummy authorization scheme can be configured using the following recipe.

Required bundles

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

Execute

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}

Verify

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.