oso could use tokens stored in another system from within your policy to make authorization decisions. However, it isn't a secrets management tool, so we would

oso could use tokens stored in another system from within your policy to make authorization decisions. However, it isn't a secrets management tool, so we wouldn't recommend using it to store authorization tokens for the same reason you wouldn't store them in your codebase.