[1/2] syncope git commit: Some integration tests improvements
Repository: syncope Updated Branches: refs/heads/master 7af5e995d -> f19e261cf http://git-wip-us.apache.org/repos/asf/syncope/blob/f19e261c/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RealmsITCase.java -- diff --git a/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RealmsITCase.java b/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RealmsITCase.java index ec17ed3..c44f52a 100644 --- a/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RealmsITCase.java +++ b/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RealmsITCase.java @@ -28,11 +28,8 @@ import org.apache.syncope.client.console.panels.TogglePanel; import org.apache.wicket.Component; import org.apache.wicket.util.tester.FormTester; import org.junit.Before; -import org.junit.FixMethodOrder; import org.junit.Test; -import org.junit.runners.MethodSorters; -@FixMethodOrder(MethodSorters.JVM) public class RealmsITCase extends AbstractConsoleITCase { @Before @@ -113,9 +110,9 @@ public class RealmsITCase extends AbstractConsoleITCase { TESTER.executeAjaxEvent("body:content:realmChoicePanel:container:realms:btn", Constants.ON_CLICK); TESTER.executeAjaxEvent("body:content:realmChoicePanel:container:realms:dropdown-menu:buttons:3:button", Constants.ON_CLICK); - + TESTER.assertLabel("body:content:realmChoicePanel:container:realm", "/odd"); - + TESTER.clickLink( "body:content:body:container:content:tabbedPanel:panel:actions:actions:panelTemplate:templateLink"); TESTER.assertComponent("body:content:toggleTemplates", TogglePanel.class); @@ -133,7 +130,7 @@ public class RealmsITCase extends AbstractConsoleITCase { TESTER.assertInfoMessages("Operation executed successfully"); TESTER.cleanupFeedbackMessages(); - + TESTER.assertLabel("body:content:realmChoicePanel:container:realm", "/odd"); TESTER.clickLink( @@ -149,7 +146,7 @@ public class RealmsITCase extends AbstractConsoleITCase { TESTER.assertModelValue("body:content:templateModal:form:content:form:view:username:textField", "'k' + firstname"); - + formTester = TESTER.newFormTester("body:content:templateModal:form:content:form"); formTester.setValue("view:username:textField", ""); formTester.submit("buttons:finish"); @@ -192,10 +189,10 @@ public class RealmsITCase extends AbstractConsoleITCase { TESTER.assertModelValue("body:content:body:outerObjectsRepeater:0:outer:form:content:customResultBody:" + "secondLevelContainer:second:remoteObject:propView:0:value:oldAttribute:textField", null); - + TESTER.assertModelValue("body:content:body:outerObjectsRepeater:0:outer:form:content:customResultBody:" + "secondLevelContainer:second:remoteObject:propView:1:value:oldAttribute:textField", null); - + TESTER.assertModelValue("body:content:body:outerObjectsRepeater:0:outer:form:content:customResultBody:" + "secondLevelContainer:second:remoteObject:propView:2:value:oldAttribute:textField", null); @@ -253,10 +250,10 @@ public class RealmsITCase extends AbstractConsoleITCase { TESTER.assertModelValue("body:content:body:outerObjectsRepeater:0:outer:form:content:customResultBody:" + "secondLevelContainer:second:remoteObject:propView:1:value:newAttribute:textField", null); - + TESTER.assertModelValue("body:content:body:outerObjectsRepeater:0:outer:form:content:customResultBody:" + "secondLevelContainer:second:remoteObject:propView:2:value:newAttribute:textField", null); - + TESTER.clickLink("body:content:body:outerObjectsRepeater:0:outer:form:content:customResultBody:" + "secondLevelContainer:back"); http://git-wip-us.apache.org/repos/asf/syncope/blob/f19e261c/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RelationshipTypeITCase.java -- diff --git a/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RelationshipTypeITCase.java b/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RelationshipTypeITCase.java deleted file mode 100644 index 0f9af86..000 --- a/fit/core-reference/src/test/java/org/apache/syncope/fit/console/RelationshipTypeITCase.java +++ /dev/null @@ -1,124 +0,0 @@ -/* - * Licensed to the Apache Software Foundation (ASF) under one - * or more contributor license agreements. See the NOTICE file - * distributed with this work for additional information - * regarding copyright ownership. The ASF licenses this file - * to you under the Apache License, Version 2.0 (the - * "License"); you may not use this file except in
syncope git commit: Capitalising some of the concepts
Repository: syncope Updated Branches: refs/heads/master a81d6121d -> 7af5e995d Capitalising some of the concepts Project: http://git-wip-us.apache.org/repos/asf/syncope/repo Commit: http://git-wip-us.apache.org/repos/asf/syncope/commit/7af5e995 Tree: http://git-wip-us.apache.org/repos/asf/syncope/tree/7af5e995 Diff: http://git-wip-us.apache.org/repos/asf/syncope/diff/7af5e995 Branch: refs/heads/master Commit: 7af5e995d60f30b500f4496ea3672c67d2a51d01 Parents: a81d612 Author: Colm O hEigeartaighAuthored: Thu Aug 11 11:49:58 2016 +0100 Committer: Colm O hEigeartaigh Committed: Thu Aug 11 11:49:58 2016 +0100 -- .../asciidoc/getting-started/introduction.adoc | 12 .../getting-started/systemRequirements.adoc | 2 +- .../reference-guide/architecture/core.adoc | 8 +++--- .../reference-guide/concepts/entitlements.adoc | 4 +-- .../concepts/externalresources.adoc | 20 ++--- .../reference-guide/concepts/policies.adoc | 28 +- .../concepts/provisioning/propagation.adoc | 10 +++ .../concepts/provisioning/provisioning.adoc | 2 +- .../concepts/provisioning/pull.adoc | 10 +++ .../concepts/provisioning/push.adoc | 4 +-- .../reference-guide/concepts/realms.adoc| 16 +-- .../reference-guide/concepts/roles.adoc | 10 +++ .../concepts/typemanagement.adoc| 30 ++-- .../concepts/usersgroupsandanyobjects.adoc | 20 ++--- .../reference-guide/concepts/workflow.adoc | 6 ++-- .../identitytechnologies/accessmanagers.adoc| 4 +-- .../identitytechnologies/identitystores.adoc| 8 +++--- .../provisioningengines.adoc| 8 +++--- .../thecompletepicture.adoc | 2 +- .../reference-guide/reference-guide.adoc| 2 +- .../adminconsole/configuration.adoc | 4 +-- .../adminconsole/dashboard.adoc | 4 +-- .../adminconsole/extensions.adoc| 2 +- .../adminconsole/realms.adoc| 4 +-- .../workingwithapachesyncope/cli/group.adoc | 6 ++-- .../workingwithapachesyncope/cli/user.adoc | 16 +-- 26 files changed, 121 insertions(+), 121 deletions(-) -- http://git-wip-us.apache.org/repos/asf/syncope/blob/7af5e995/src/main/asciidoc/getting-started/introduction.adoc -- diff --git a/src/main/asciidoc/getting-started/introduction.adoc b/src/main/asciidoc/getting-started/introduction.adoc index bb06b5e..88f27c3 100644 --- a/src/main/asciidoc/getting-started/introduction.adoc +++ b/src/main/asciidoc/getting-started/introduction.adoc @@ -50,10 +50,10 @@ In brief, Identity Management takes care of managing identity data throughout wh [.text-center] image::identityLifecycle.png[title="Identity Lifecycle",alt="Identity Lifecycle",width="505",height="324"] -.Users, groups and any objects +.Users, Groups and Any Objects -With Apache Syncope 2.0.0, the managed identities are not limited anymore to users and groups. New object types can be -defined so that any objects data can be managed through Syncope: workstations, printers, folders, sensors, services, +With Apache Syncope 2.0.0, the managed identities are not limited anymore to Users and Groups. New object types can be +defined so that Any Object's data can be managed through Syncope: workstations, printers, folders, sensors, services, and so on. This positions Apache Syncope at the forefront for bringing Identity Management in the IoT world. @@ -65,7 +65,7 @@ image::iam-scenario.png[title="IAM Scenario",alt="IAM Scenario"] The picture above shows the tecnologies involved in a complete IAM solution: * *_Identity Store_* (as RDBMS, LDAP, Active Directory, meta- and virtual-directories) - the repository for account data -* *_Provisioning Engine_* - synchronizes account data across identity stores and a broad range of data formats, models, +* *_Provisioning Engine_* - synchronizes account data across Identity Stores and a broad range of data formats, models, meanings and purposes * *_Access Manager_* - access mediator to all applications, focused on application front-end, taking care of authentication (https://en.wikipedia.org/wiki/Single_sign-on[Single Sign-On^]), authorization @@ -79,7 +79,7 @@ From a technology point of view, *Apache Syncope* is primarily a *Provisioning E Aren't Identity Stores enough? -One might suppose that a single identity store can solve all the identity needs inside an organization, but there +One might suppose that a single Identity Store can solve all the identity needs inside an organization, but there are a few drawbacks with this approach: .
syncope git commit: Fixing issue raised by Francesco
Repository: syncope Updated Branches: refs/heads/master dae8e14a7 -> a81d6121d Fixing issue raised by Francesco Project: http://git-wip-us.apache.org/repos/asf/syncope/repo Commit: http://git-wip-us.apache.org/repos/asf/syncope/commit/a81d6121 Tree: http://git-wip-us.apache.org/repos/asf/syncope/tree/a81d6121 Diff: http://git-wip-us.apache.org/repos/asf/syncope/diff/a81d6121 Branch: refs/heads/master Commit: a81d6121d18479c275ada58cdb2bbd8f8b8072b6 Parents: dae8e14 Author: Colm O hEigeartaighAuthored: Thu Aug 11 11:33:27 2016 +0100 Committer: Colm O hEigeartaigh Committed: Thu Aug 11 11:33:27 2016 +0100 -- src/main/asciidoc/reference-guide/concepts/typemanagement.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) -- http://git-wip-us.apache.org/repos/asf/syncope/blob/a81d6121/src/main/asciidoc/reference-guide/concepts/typemanagement.adoc -- diff --git a/src/main/asciidoc/reference-guide/concepts/typemanagement.adoc b/src/main/asciidoc/reference-guide/concepts/typemanagement.adoc index 044f196..e0878db 100644 --- a/src/main/asciidoc/reference-guide/concepts/typemanagement.adoc +++ b/src/main/asciidoc/reference-guide/concepts/typemanagement.adoc @@ -154,7 +154,7 @@ given user / group / any object instance) and for < > can be selected so that instances af a given any type will +For all any types that are defined, a set of < > can be selected so that instances af a given any type will be enabled to populate attributes for schemas in those classes. .Any types and attributes allowed for users, groups and any objects
syncope git commit: More grammatical work on the reference guide
Repository: syncope Updated Branches: refs/heads/master 9aea42ba0 -> dae8e14a7 More grammatical work on the reference guide Project: http://git-wip-us.apache.org/repos/asf/syncope/repo Commit: http://git-wip-us.apache.org/repos/asf/syncope/commit/dae8e14a Tree: http://git-wip-us.apache.org/repos/asf/syncope/tree/dae8e14a Diff: http://git-wip-us.apache.org/repos/asf/syncope/diff/dae8e14a Branch: refs/heads/master Commit: dae8e14a747b1501072a6cce991f954e01dc6098 Parents: 9aea42b Author: Colm O hEigeartaighAuthored: Thu Aug 11 11:05:03 2016 +0100 Committer: Colm O hEigeartaigh Committed: Thu Aug 11 11:05:03 2016 +0100 -- .../concepts/externalresources.adoc | 40 ++-- .../concepts/typemanagement.adoc| 31 +++ 2 files changed, 36 insertions(+), 35 deletions(-) -- http://git-wip-us.apache.org/repos/asf/syncope/blob/dae8e14a/src/main/asciidoc/reference-guide/concepts/externalresources.adoc -- diff --git a/src/main/asciidoc/reference-guide/concepts/externalresources.adoc b/src/main/asciidoc/reference-guide/concepts/externalresources.adoc index 0fc4f9a..ef2cdd4 100644 --- a/src/main/asciidoc/reference-guide/concepts/externalresources.adoc +++ b/src/main/asciidoc/reference-guide/concepts/externalresources.adoc @@ -23,7 +23,7 @@ Connector Bundles:: The components able to connect to identity stores; not speci as they are part of the http://connid.tirasa.net[ConnId^] project. Connector Instances:: Instances of connector bundles, obtained by assigning values to the defined configuration properties. For instance, there is only a single `DatabaseTable` (the bundle) that can be instantiated -several times, for example if there is need to connect to different databases. +several times, for example if there is a need to connect to different databases. External Resources:: Meant to encapsulate all information about how Apache Syncope will use connector instances for provisioning. For each entity supported by the related connector bundle (user, group, printer, services, ...), < > information can be specified. @@ -46,7 +46,7 @@ be JDBC URL, table name, etc. * capabilities - define what operations are allowed on this connector: during < >, if a certain operation is invoked but the corresponding capability is not set on the related connector instance, no actual action is performed on the underlying connector; the capabilities are: -** `AUTHENTICATE` - consent < > +** `AUTHENTICATE` - consent to < > ** `CREATE` - create objects on the underlying connector ** `UPDATE` - update objects on the underlying connector ** `DELETE` - delete objects on the underlying connector @@ -61,16 +61,16 @@ action is performed on the underlying connector; the capabilities are: Capabilities and individual configuration properties can be set for _override_: in this case, all the external resources using the given connector instance will have the chance to override some configuration values, or the capabilities set. -This can be useful when the same connector instance is shared among different resources, with small difference in the +This can be useful when the same connector instance is shared among different resources, with little difference in the required configuration or capabilities. External Resource details -Given a selected connector instance, the following information is required for defining an external resource: +Given a selected connector instance, the following information is required to define an external resource: * priority - integer value, in use by the default < > -* generate random password flag - under some circumstances, password might be mandatory but no actual value could be +* generate random password flag - under some circumstances, a password might be mandatory but no actual value could be available: with this flag set, a random value will be generated, compliant with the defined < > (if set) * propagation actions - which < > shall be executed during propagation @@ -89,19 +89,19 @@ resource Mapping -One of the most crucial information to provide, when configuring an external resource, is the mapping between internal -and external data. Such information, in fact, plays a key role for < >. +The mapping between internal and external data is of crucial importance when +configuring an external resource. Such information, in fact, plays a key role for
syncope git commit: [SYNCOPE-700] Backporting some grammar fixes from 15c34e7644fb797dff42ab7e9e153d2264da9cd2 to getting started
Repository: syncope Updated Branches: refs/heads/master 15c34e764 -> 9aea42ba0 [SYNCOPE-700] Backporting some grammar fixes from 15c34e7644fb797dff42ab7e9e153d2264da9cd2 to getting started Project: http://git-wip-us.apache.org/repos/asf/syncope/repo Commit: http://git-wip-us.apache.org/repos/asf/syncope/commit/9aea42ba Tree: http://git-wip-us.apache.org/repos/asf/syncope/tree/9aea42ba Diff: http://git-wip-us.apache.org/repos/asf/syncope/diff/9aea42ba Branch: refs/heads/master Commit: 9aea42ba0b7744a822ec9ca14e6eb5ca0c142455 Parents: 15c34e7 Author: Francesco ChicchiriccòAuthored: Thu Aug 11 08:25:27 2016 +0200 Committer: Francesco Chicchiriccò Committed: Thu Aug 11 08:25:27 2016 +0200 -- src/main/asciidoc/getting-started/introduction.adoc | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) -- http://git-wip-us.apache.org/repos/asf/syncope/blob/9aea42ba/src/main/asciidoc/getting-started/introduction.adoc -- diff --git a/src/main/asciidoc/getting-started/introduction.adoc b/src/main/asciidoc/getting-started/introduction.adoc index 63a8f8f..bb06b5e 100644 --- a/src/main/asciidoc/getting-started/introduction.adoc +++ b/src/main/asciidoc/getting-started/introduction.adoc @@ -74,20 +74,20 @@ authentication (https://en.wikipedia.org/wiki/Single_sign-on[Single Sign-On^]), [NOTE] -Technologically, *Apache Syncope* is primarily a *Provisioning Engine*. +From a technology point of view, *Apache Syncope* is primarily a *Provisioning Engine*. Aren't Identity Stores enough? -One might suppose that a single identity store can solve all the identity needs inside an organization, but few -drawbacks are just around the corner: +One might suppose that a single identity store can solve all the identity needs inside an organization, but there +are a few drawbacks with this approach: . Heterogeneity of systems . Lack of a single source of information (HR for corporate id, Groupware for mail address, ...) . Often applications require a local user database . Inconsistent policies across the infrastructure . Lack of workflow management -. Hidden infrastructure management cost, growing with organization +. Hidden infrastructure management cost, growing with the size of the organization === A bird's eye view on the Architecture @@ -108,7 +108,7 @@ https://en.wikipedia.org/wiki/Representational_state_transfer[RESTful^] interfac written in any programming language, to consume IdM services. * *_Logic_* implements the overall business logic that can be triggered via REST services, and controls some additional -features (notifications, reports and audit over all) +features (notifications, reports and auditing) * *_Provisioning_* is involved with managing the internal (via workflow) and external (via specific connectors) representation of users, groups and any objects. + This component often needs to be tailored to meet the requirements of a specific deployment, as it is the crucial decision