Update Trust(s)

patch

/v2/trust

Update a list of Trust documents.

Request

Supported Media Types
Body ()
The list of Trust objects (without any sub objects) with new values for those updatable fileds, for now only displayname is uptable.
Root Schema : schema
Type: array
Show Source
Nested Schema : Trust
Type: object
Trust Model Object
Show Source
Nested Schema : issuers
Type: array
The list of all TokenIssuer sub objects
Show Source
Nested Schema : tokenAttributeRules
Type: array
The list of all TokenAttributeRule sub objects
Show Source
Nested Schema : TokenIssuer
Type: object
TokenIssuer Model Object
Show Source
Nested Schema : DiscoveryInfo
Type: object
DiscoveryInfo Model Object.
Show Source
Nested Schema : relyingparties
Type: array
The list of all RelyingParty sub objects
Show Source
Nested Schema : TrustedKey
Type: object
TrustedKey Model Object.
Show Source
  • keyidentifiers
    A list of KeyIdentifier sub objects. They are either fetched from location that is specified by mdurl or being manually added.
  • Read Only: true
  • Read Only: true
  • Metadata URL of a TrustedKey. This field is only valid when the tokentype of its SwaggerObject.TOKENISSUER is jwt.
  • An integer value indicates how often key identifiers need to be refetched from location specified by field mdurl
  • Allowed Values: [ "dns.jwt", "jwk.jwt", "idcs.dns.jwt", "idcs.jwk.jwt" ]
    Trust type of TrustedKey. This field is only valid when the tokentype of its SwaggerObject.TOKENISSUER is jwt. and mdurl is set. It must be one of the allowed predefined value.
Nested Schema : RelyingParty
Type: object
RelyingParty Model Object.
Show Source
Nested Schema : keyidentifiers
Type: array
A list of KeyIdentifier sub objects. They are either fetched from location that is specified by mdurl or being manually added.
Show Source
Nested Schema : KeyIdentifier
Type: object
KeyIdentifier Model Object.
Show Source
  • Allowed Values: [ "true", "false" ]
    ture indicates KeyIdentifier is enabled, false otherwise, default is true.
  • Allowed Values: [ "x509certificate", "symmetricKey", "publicKey" ]
    Key type of an KeyIdentifier. It must be one of the predefined allowable values, which one is valid depends on its Issuer's token type. The valid combinations are: 1. keytype must bex509certificate if its parent TokenIssuer is either saml.hok or saml.sv. 2. keytype can be x509certificate,symmetricKey or publicKey if its parent TokenIssuer is jwt.
    Example: x509certificate
  • Value of an KeyIdentifier
  • Allowed Values: [ "dn", "alias", "csfkey", "kid" ]
    Value type of an KeyIdentifier, First it must be one of the predefined allowable values, and second, which one is valid depends on its corresponding field keytype The valid combinations are: it can be dn or alias if its keytype is x509certificate it can only be csfkey if its keytype is symmetricKey it can only be kid if its keytype is publicKey
Nested Schema : TokenAttributeRule
Type: object
TokenAttributeRule Model Object
Show Source
Nested Schema : attributes
Type: array
The list of all TokenAttribute sub objects
Show Source
Nested Schema : NameId
Type: object
NameId Model Object
Show Source
Nested Schema : Proxy
Type: object
Proxy Model Object.
Show Source
Nested Schema : VirtualUser
Type: object
VirtualUser Model Object.
Show Source
Nested Schema : TokenAttribute
Type: object
TokenAttribute Model Object
Show Source
Nested Schema : filter
Type: array
Filter
Show Source
Example:
['filter1', 'filter2']
Nested Schema : AttributeMapping
Type: object
AttributeMapping Model Object.
Show Source
Nested Schema : filter
Type: array
Filter
Show Source
Example:
['filter1', 'filter2']
Nested Schema : defaultRoles
Type: array
An array of default roles of a VirtualUser
Show Source
Nested Schema : tokenRoleAttributes
Type: array
Show Source
Nested Schema : tokenRoleMappings
Type: array
A list of TokenRoleMapping sub objects
Show Source
Nested Schema : TokenRoleMapping
Type: object
TokenRoleMapping Model Object.
Show Source
Nested Schema : mappingRoles
Type: array
List of role mappings.
Show Source
Example:
['roleMapping1', 'roleMpping2']
Back to Top

Response

Supported Media Types

200 Response

successful operation
Body ()
Root Schema : ResponseStatus
Type: object
ResponseStatus model object.
Show Source
  • Detail message of the response, if response is successful, its a confirmation, otherwise it is an error message indicating the root cause.
    Example: PolicySets [myPolicyset1, myPolicyset2] are successfully created.
  • Allowed Values: [ "20001", "20002", "20003", "20004", "20005", "20011", "20012", "20013", "20014", "20021", "20023", "20024", "20032", "20033", "20034", "20035", "20042", "20043", "20044", "20051", "20052", "20053", "20054", "20055", "20061", "20062", "20063", "20064", "20065", "20071", "20072", "20073", "20074", "20075", "20081", "20082", "20083", "20084", "20085", "20091", "20092", "20093", "20094", "20095", "20101", "20102", "20103", "20104", "20105", "20111", "20112", "20113", "20114", "20115", "20121", "20122", "20123", "20124", "20125", "20131", "20132", "20133", "20134", "20135", "20141", "20142", "20143", "20144", "20145", "20151", "20152", "20153", "20154", "20155", "20161", "20162", "20163", "20164", "20165", "20171", "20172", "20173", "20174", "20175", "40001", "40002", "40003", "40004", "40011", "40012", "40013", "40014", "40021", "40023", "40024", "40032", "40033", "40042", "40043", "40044", "40051", "40052", "40053", "40054", "40061", "40062", "40063", "40064", "40071", "40072", "40073", "40074", "40081", "40082", "40083", "40084", "40091", "40092", "40093", "40094", "40101", "40102", "40103", "40104", "40111", "40112", "40113", "40114", "40121", "40122", "40123", "40124", "40131", "40132", "40133", "40134", "40141", "40142", "40143", "40144", "40151", "40152", "40153", "40154", "40161", "40162", "40163", "40164", "40171", "40172", "40173", "40174" ]
    OWSM Rest API status code for operations on various APIs. One can write tests and parse the status code based on the rules below. If you plan to process the status code programmatically, you can access the OWSM source file for the constants defined at: oracle.wsm.resources.rest.RestMessageID.java. Status Code Pattern:first digit from left indicates the operation status, 2=successful, 4=failed last digit indicate operation 1=POST, 2=PUT, 3=GET, 4=DELETE, 5=DELETE NONE. second, third, fourth digits from left are used for OWSM Rest API Resource types: 000=PolicySet, 001=PolicyReference, 002=ConfigOverride, 003=Configuration, 004=Repository (not used yet), 005=Trust, 006=Issuer, 007=TrustedKey, 008=KeyIdentifier, 009=RelyingParty, 010=AttributeRule, 011=Attribute, 012=VirtualUser, 013=RoleMapping, 014=Mapping, 015=NamedID, 016=DiscoveryInfo, 017=Proxy
    Example: 20001

400 Response

User bad request, please correct input data and try again.
Body ()
Root Schema : ResponseStatus
Type: object
ResponseStatus model object.
Show Source
  • Detail message of the response, if response is successful, its a confirmation, otherwise it is an error message indicating the root cause.
    Example: PolicySets [myPolicyset1, myPolicyset2] are successfully created.
  • Allowed Values: [ "20001", "20002", "20003", "20004", "20005", "20011", "20012", "20013", "20014", "20021", "20023", "20024", "20032", "20033", "20034", "20035", "20042", "20043", "20044", "20051", "20052", "20053", "20054", "20055", "20061", "20062", "20063", "20064", "20065", "20071", "20072", "20073", "20074", "20075", "20081", "20082", "20083", "20084", "20085", "20091", "20092", "20093", "20094", "20095", "20101", "20102", "20103", "20104", "20105", "20111", "20112", "20113", "20114", "20115", "20121", "20122", "20123", "20124", "20125", "20131", "20132", "20133", "20134", "20135", "20141", "20142", "20143", "20144", "20145", "20151", "20152", "20153", "20154", "20155", "20161", "20162", "20163", "20164", "20165", "20171", "20172", "20173", "20174", "20175", "40001", "40002", "40003", "40004", "40011", "40012", "40013", "40014", "40021", "40023", "40024", "40032", "40033", "40042", "40043", "40044", "40051", "40052", "40053", "40054", "40061", "40062", "40063", "40064", "40071", "40072", "40073", "40074", "40081", "40082", "40083", "40084", "40091", "40092", "40093", "40094", "40101", "40102", "40103", "40104", "40111", "40112", "40113", "40114", "40121", "40122", "40123", "40124", "40131", "40132", "40133", "40134", "40141", "40142", "40143", "40144", "40151", "40152", "40153", "40154", "40161", "40162", "40163", "40164", "40171", "40172", "40173", "40174" ]
    OWSM Rest API status code for operations on various APIs. One can write tests and parse the status code based on the rules below. If you plan to process the status code programmatically, you can access the OWSM source file for the constants defined at: oracle.wsm.resources.rest.RestMessageID.java. Status Code Pattern:first digit from left indicates the operation status, 2=successful, 4=failed last digit indicate operation 1=POST, 2=PUT, 3=GET, 4=DELETE, 5=DELETE NONE. second, third, fourth digits from left are used for OWSM Rest API Resource types: 000=PolicySet, 001=PolicyReference, 002=ConfigOverride, 003=Configuration, 004=Repository (not used yet), 005=Trust, 006=Issuer, 007=TrustedKey, 008=KeyIdentifier, 009=RelyingParty, 010=AttributeRule, 011=Attribute, 012=VirtualUser, 013=RoleMapping, 014=Mapping, 015=NamedID, 016=DiscoveryInfo, 017=Proxy
    Example: 20001

500 Response

Operation failed with unexpected error.
Body ()
Root Schema : ResponseStatus
Type: object
ResponseStatus model object.
Show Source
  • Detail message of the response, if response is successful, its a confirmation, otherwise it is an error message indicating the root cause.
    Example: PolicySets [myPolicyset1, myPolicyset2] are successfully created.
  • Allowed Values: [ "20001", "20002", "20003", "20004", "20005", "20011", "20012", "20013", "20014", "20021", "20023", "20024", "20032", "20033", "20034", "20035", "20042", "20043", "20044", "20051", "20052", "20053", "20054", "20055", "20061", "20062", "20063", "20064", "20065", "20071", "20072", "20073", "20074", "20075", "20081", "20082", "20083", "20084", "20085", "20091", "20092", "20093", "20094", "20095", "20101", "20102", "20103", "20104", "20105", "20111", "20112", "20113", "20114", "20115", "20121", "20122", "20123", "20124", "20125", "20131", "20132", "20133", "20134", "20135", "20141", "20142", "20143", "20144", "20145", "20151", "20152", "20153", "20154", "20155", "20161", "20162", "20163", "20164", "20165", "20171", "20172", "20173", "20174", "20175", "40001", "40002", "40003", "40004", "40011", "40012", "40013", "40014", "40021", "40023", "40024", "40032", "40033", "40042", "40043", "40044", "40051", "40052", "40053", "40054", "40061", "40062", "40063", "40064", "40071", "40072", "40073", "40074", "40081", "40082", "40083", "40084", "40091", "40092", "40093", "40094", "40101", "40102", "40103", "40104", "40111", "40112", "40113", "40114", "40121", "40122", "40123", "40124", "40131", "40132", "40133", "40134", "40141", "40142", "40143", "40144", "40151", "40152", "40153", "40154", "40161", "40162", "40163", "40164", "40171", "40172", "40173", "40174" ]
    OWSM Rest API status code for operations on various APIs. One can write tests and parse the status code based on the rules below. If you plan to process the status code programmatically, you can access the OWSM source file for the constants defined at: oracle.wsm.resources.rest.RestMessageID.java. Status Code Pattern:first digit from left indicates the operation status, 2=successful, 4=failed last digit indicate operation 1=POST, 2=PUT, 3=GET, 4=DELETE, 5=DELETE NONE. second, third, fourth digits from left are used for OWSM Rest API Resource types: 000=PolicySet, 001=PolicyReference, 002=ConfigOverride, 003=Configuration, 004=Repository (not used yet), 005=Trust, 006=Issuer, 007=TrustedKey, 008=KeyIdentifier, 009=RelyingParty, 010=AttributeRule, 011=Attribute, 012=VirtualUser, 013=RoleMapping, 014=Mapping, 015=NamedID, 016=DiscoveryInfo, 017=Proxy
    Example: 20001
Back to Top