At present the reference server implementation of FIRES only supports public datasets. For some people using FIRES, non-public datasets may be desirable. This is already supported* by the protocol, as it's just HTTP, so you could just use Basic Auth or proxy with Bearer tokens, but it's not natively supported, and we could change that.
Related issues:
On the protocol side, it'd mostly be documenting how to challenge for authentication (WWW-Authenticate?)
In server implementation, Access Tokens are probably the easiest to add, since I already have infrastructure in place for them, HTTP Message Signatures would be more complex.
At present the reference server implementation of FIRES only supports public datasets. For some people using FIRES, non-public datasets may be desirable. This is already supported* by the protocol, as it's just HTTP, so you could just use Basic Auth or proxy with Bearer tokens, but it's not natively supported, and we could change that.
Related issues:
On the protocol side, it'd mostly be documenting how to challenge for authentication (WWW-Authenticate?)
In server implementation, Access Tokens are probably the easiest to add, since I already have infrastructure in place for them, HTTP Message Signatures would be more complex.