1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.
//
// SPDX-License-Identifier: Apache-2.0
//! Identity Config configuration
use ;
use AsyncOpenStack;
use crate::;
/// Config configuration
///
/// You can manage domain-specific configuration options.
///
/// Config-specific configuration options are structured within their group objects. The API
/// supports only the identity and ldap groups. These groups override the default configuration
/// settings for the storage of users and groups by the Identity server.
///
/// You can create, update, and delete domain-specific configuration options by using the HTTP PUT
/// , PATCH , and DELETE methods. When updating, it is only necessary to include those options that
/// are being updated.
///
/// To create an option, use the PUT method. The Identity API does not return options that are
/// considered sensitive, although you can create and update these options. The only option
/// currently considered sensitive is the password option within the ldap group.
///
/// The API enables you to include sensitive options as part of non- sensitive options. For
/// example, you can include the password as part of the url option.
///
/// If you try to create or update configuration options for groups other than whitelisted on the
/// server side, the Forbidden (403) response code is returned.
///
/// For information about how to integrate the Identity service with LDAP, see Integrate Identity
/// with LDAP.
///
/// A domain is a collection of users, groups, and projects. Each group and project is owned by
/// exactly one domain.
/// Supported subcommands