Do you think it would be a viable workaround to treat machine users as regular users in the Supertokens, and treat the user id as a client id (which we generate) and the password as the client secret (which we also generate) and we create an auth endpoint on our app which would receive the client id and client secret then auth against Supertokens and returnan access token to the client? Basically this: