Incorrect example in federated rules documentation

[Marek Denis]

There is a major error in one of the examples in the mapping rules documentation [0]

When mapping groups by names along with blacklist/whitelist keywords the correct structure is:

            "local": [
                {
                    "groups": "{0}",
                    "domain": {
                        "id": DEVELOPER_GROUP_DOMAIN_ID
                    }
                },
]

whereas one can find following in the documentation:

"local": [
                {
                    "groups": {
                        "name": "{1}",
                        "domain": {
                            "id": "0cd5e9"
                        }
                    }
                }
            ],

This should be fixed as soon as possible as uses following guidance will fail with their setup.

[0] http://docs.openstack.org/developer/keystone/mapping_combinations.html

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/237479

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/237479
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=dd3ef9ddd284bd5c6d92ec73029f87275ee3d741
Submitter: Jenkins
Branch: master

commit dd3ef9ddd284bd5c6d92ec73029f87275ee3d741
Author: Marek Denis <email address hidden>
Date: Tue Oct 20 11:16:04 2015 +0200

    Fix incorrect federated mapping example

    The documentation didn't provide correct example of a mapping rules with
    direct group mapping (with blacklist/whitelist keyword).
    This could led users to a major confusion.

    The example is now fixed. Additionaly, for clarity and increased
    readibility the ``user`` and ``groups``
    objects were split into separate ``local`` rules.

    Change-Id: Iff343f1ff2829ef282a1314fd07203a435611e70
    Closes-Bug: #1507944

[Thierry Carrez (ttx)]

This issue was fixed in the openstack/keystone 9.0.0.0b1 development milestone.