summaryrefslogtreecommitdiff
path: root/keystone/federation/schema.py
Commit message (Collapse)AuthorAgeFilesLines
* Expiring Group Memberships API - Allow set idp authorization_ttlKristi Nikolla2020-04-091-0/+2
| | | | | | | | This patch extends the identity provider API to receive, return and set the authorization_ttl on an identity provider. Change-Id: I3c58da290d52149e307280042ed20447da4687f7 Partial-Bug: 1809116
* Add new attribute to the federation protocol APIerus2019-07-191-1/+7
| | | | | | | | | | | | | | Modify the FederationProtocolModel class and add the remote_id_atributte to the federation_protocol table. Add the respective migration and tests files. And also modify the schema to expect a remote_id_attribute property. Closes-bug: #1724645 Co-authored-by: Colleen Murphy<colleen@gazlene.net> Change-Id: I9802c8a5c187bae16de89893ca8639b01cd7cb1b
* Require domain_id when registering Identity ProvidersRonald De Rose2017-01-061-3/+16
| | | | | | | | | | | | | An Identity Provider (IdP) should be related (1:1) to a domain so that federated users properly belong to a domain and can be uniquely identified by their domain + unique_id. This patch makes it so that a domain_id is required when registering a new IdP. If not explicitly set via the API, the IdP will be mapped to a newly created domain. The docs and release notes will be added in a subsequent patch. Partial-Bug: #1642687 Partially-Implements: bp support-federated-attr Change-Id: Id18b8b2fe853b97631bc990df8188ed64a6e1275
* Separate protocol schemaLance Bragstad2016-05-081-5/+13
| | | | | | | | | Currently, the protocol entity is validated using the same schema regardless of the request creating or updating a protocol. All other schemas in keystone break the schemas into create and update schemas. This applies that same convention to the federated protocol entities. Change-Id: Ic6f481cdb4147c2068c4378cf9e398a3db6eeb63
* Allow '_' character in mapping_id valueRoxana Gherle2016-01-291-1/+1
| | | | | | | Underscore character should be allowed in mapping_id. Closes-Bug: #1531959 Change-Id: I4235e09ff68f68bbe4cf5c4e9aeaef2b79484f94
* Add schema for federation protocolDave Chen2016-01-051-0/+10
| | | | | | | | Add schema validation on create/update of federation protocol. Partially implements: bp schema-validation-extent Change-Id: I460dfdd18cb3a044f9f9dde4ba23b268864543b8
* Add schema for identity providerDave Chen2015-12-311-0/+26
| | | | | | | | Add schema validation on create/update of identity provider. Partially implements: bp schema-validation-extent Change-Id: I53462b0f93f445a0121f5b1e8c69538fa4afd853
* Move federation extension into keystone coreSteve Martinelli2015-11-181-0/+79
Remove federation as an extension and move it to a core resource. For now we leave the database migrations in the extension directory until we have a general policy for merging these into core. Some instances of federation constants were removed because they were causing a circular dependency, these can be refactored in a later patch. DocImpact: You should no longer run the migrations for this extension Implements: bp move-extensions Co-Authored-By: Nithya Renganathan <narengan@us.ibm.com> Change-Id: If5857a6ee4c7c527929069b25beab40f4c5d87e2
View Lorry Controller Status