You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following endpoints require elevation to be used under any circumstances:
createUser
getUserByUserId
updateUser
replaceUser
deleteUser
createUserGroup
patchUserGroup
putUserGroup
deleteUserGroup
importBenchmark
deleteRevisionByString
deleteStigById
getUsers: Requires elevation to use any projections.
getUserGroups: Elevation required for "collections" projection.
getUserGroup: Elevation required for "collections" projection.
Notes about how elevation effects other endpoints (please dont take this as 100% correct):
getCollections
"statistics" projection: Response data changes, object is the same.
output varies depending on elevation.
createCollection
Requires elevation if the user lacks the create_collection privilege.
getCollection
Projections whos output is affected by elevation:
"statistics"
"assets"
"stigs"
"labels"
updateCollection
Requires elevation for:
Modifying owner grants.
same rules for projections as getCollection
replaceCollection
Same elevation requirements as updateCollection.
same rules for projections as getCollection
deleteCollection
Elevation affects functionality in the same way as getCollection.
getGrantsByCollection
Requires elevation for users with access level < 3.
postGrantsByCollection
Requires elevation for users with access level < 3.
Requires elevation and level 4 access to create level 4 grants.
getGrantByCollectionGrant
Requires elevation for users with access level < 3.
putGrantByCollectionGrant
Requires elevation for users with access level < 3.
Requires elevation and level 4 access to modify level 4 grants.
deleteGrantByCollectionGrant
Requires elevation for users with access level < 3.
Requires elevation and level 4 access to remove level 4 grants.
getSTIGs
Elevation alters the output.
getStigById
Elevation alters the output.
getRevisionsByBenchmarkId
Elevation alters the output.
getRevisionByString
Elevation alters the output.
These endpoints specify elevate as a parameter in the OAS, but elevate is ignored in implementation. They require level 3 or 4 access though it is an option in the api:
getCollectionMetadata
patchCollectionMetadata
putCollectionMetadata
getCollectionMetadataKeys
getCollectionMetadataValue
putCollectionMetadataValue
deleteCollectionMetadataKey
The text was updated successfully, but these errors were encountered:
The following endpoints require elevation to be used under any circumstances:
createUser
getUserByUserId
updateUser
replaceUser
deleteUser
createUserGroup
patchUserGroup
putUserGroup
deleteUserGroup
importBenchmark
deleteRevisionByString
deleteStigById
getUsers
: Requires elevation to use any projections.getUserGroups
: Elevation required for "collections" projection.getUserGroup
: Elevation required for "collections" projection.Notes about how elevation effects other endpoints (please dont take this as 100% correct):
getCollections
createCollection
create_collection
privilege.getCollection
updateCollection
getCollection
replaceCollection
updateCollection
.deleteCollection
getCollection
.getGrantsByCollection
postGrantsByCollection
getGrantByCollectionGrant
putGrantByCollectionGrant
deleteGrantByCollectionGrant
getSTIGs
getStigById
getRevisionsByBenchmarkId
getRevisionByString
These endpoints specify elevate as a parameter in the OAS, but elevate is ignored in implementation. They require level 3 or 4 access though it is an option in the api:
getCollectionMetadata
patchCollectionMetadata
putCollectionMetadata
getCollectionMetadataKeys
getCollectionMetadataValue
putCollectionMetadataValue
deleteCollectionMetadataKey
The text was updated successfully, but these errors were encountered: