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
From the conformance class https://api.stacspec.org/v1.0.0/ogcapi-features/extensions/transaction I can detect whether a server generally supports transactions.
What I can't detect is, whether the user (can be unauthenticated or authenticated), has permission to actually submit transactions.
In a UI, I'd like to only show a button to edit the file whenever I can be sure that the user has the actual permissions to use the transaction endpoints. This extension doesn't seem to describe this. How can we help with this?
The text was updated successfully, but these errors were encountered:
Is it https://docs.ogc.org/DRAFTS/20-002.html#options maybe? But that would require an additional HTTP request.
I'm not sure whether sending Authorization headers or similar are well supported for the OPTIONS method?
From the conformance class
https://api.stacspec.org/v1.0.0/ogcapi-features/extensions/transaction
I can detect whether a server generally supports transactions.What I can't detect is, whether the user (can be unauthenticated or authenticated), has permission to actually submit transactions.
In a UI, I'd like to only show a button to edit the file whenever I can be sure that the user has the actual permissions to use the transaction endpoints. This extension doesn't seem to describe this. How can we help with this?
The text was updated successfully, but these errors were encountered: