Struct HasuraIdentity 

pub struct HasuraIdentity {
    pub role: String,
    pub session: HashMap<String, String>,
    pub elevated: bool,
}

Who the caller is, in Hasura’s sense of the word.

This is not a database role and must not be used as one. The corpus names roles like Artist and anonymous that exist in no catalogue, and Hasura connects as one database user whatever role a request claims. What the role decides is which permissions apply and what x-hasura-role reads as inside a function; which database user the transaction runs as is settled elsewhere and separately.

Fields

role: String

The role the caller speaks as.

session: HashMap<String, String>

Session variables, stripped of the x-hasura- prefix, lowercased, and with dashes turned into underscores: user_id, allowed_ids. The same shape a verified token’s claims are reduced to, because a policy should not be able to tell which of the two it is reading.

elevated: bool

Whether the admin secret authenticated this request.

Distinct from role == "admin", which an administrator gives up the moment it asks to be treated as someone else. Hasura keeps the distinction for one purpose – a mutation marked backend_only is reachable only by a caller that proved it holds the secret, whatever role it then claims – and that is what this records.

Trait Implementations

impl Clone for HasuraIdentity

fn clone(&self) -> Self

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for HasuraIdentity

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.