Skip to content

Fix formatting issues in connector development guide #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lhaeger wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fix formatting issues in connector development guide #76

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions connectors/connid/1.x/connector-development-guide/index.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,7 @@ The connector just translates protocols and data formats.

The connector works with instances of `ConnectorObject` class.
Confusingly enough these `ConnectorObject` instances represent *objects on the resource*: accounts, groups, roles, privileges, organizational units and so on.
The `ConnectorObject` class contains a set of `Attribute`s. Each attribute has a name and one or more values.
The `ConnectorObject` class contains a set of ``Attribute``s. Each `Attribute` has a name and one or more values.
The values can be of several primitive types (see below).
Each `ConnectorObject` also has its `ObjectClass`. The `ObjectClass` is essentially a string value that define the type of the resource object.
It defines whether the object represents an account, group, role, organizational unit or anything else.
Expand Down Expand Up @@ -645,7 +645,9 @@ Resist the temptation to "normalize" the names to some common convention.
MidPoint can easily do the mapping with (almost) any attribute names in (almost) any convention.

* *type*: defines the type of the attribute: string, number, binary, etc.
This is one of several selected Java data types:** `String`
This is one of several selected Java data types:

** `String`

** `long` and `Long`

Expand Down Expand Up @@ -686,7 +688,9 @@ But it may also be useful if the original attribute name is too "fancy" and desp
E.g. if it contains national characters or something else that breaks ConnId or midPoint.
In such a case this field can be used to store the original name.

* *flags*: set of flags that define how the attribute should be used: `REQUIRED`: this is required attribute (not optional)
* *flags*: set of flags that define how the attribute should be used:

** `REQUIRED`: this is required attribute (not optional)

** `MULTIVALUED`: attribute may have more than one value

Expand Down