website logo
โŒ˜K
Introduction
Getting started
๐Ÿ“Reference
Data API
Cache API
Search API
Storage API
Queue API
Crawler API
๐Ÿ”‘Authentication
โœ”๏ธConfiguration
โšกContributing to hyper
๐Ÿ”ŒBuilding your own adapter
Code of Conduct
hyper RFCs
Style Guide
Bugs
Before Submitting A Bug Report
Building your own plugin
API Clients
Build your own client ๐Ÿ› ๏ธ
hyper connect
NodeJS Client ๐Ÿš€
Deno Client ๐Ÿฆ•
Middleware
Hooks
๐ŸšขDeploy
Deploy hyper on Render
Deploy hyper on AWS
Deploy hyper on Digital Ocean
Deploy hyper on Google Cloud
Deploy hyper on Azure
๐Ÿ“œChangelog
FAQ
๐Ÿ“•Terminology
Parameters
What is REST?
What is JSON?
๐Ÿ“˜Glossary
Docs powered byย archbeeย 
5min

Authentication

Authentication is always a tough topic to discuss, there are so many patterns out there and by supporting one, you are more than likely to fail at supporting others. With that said, we wanted to make hyper63โšก flexible so that your team can use the security model that works best for you. We also wanted to give teams an option by default. The option is using JWT hmac security, which is based on a `SECRET`.

Default๐Ÿš€

To use the default security process you will need to setup your hyper63.config.jsโšก file to use middleware and the @hyper63/app-expressโšก module as your app container.

For Example:

JS
|

And create a jwt.js file

JS
|

Custom ๐Ÿ› ๏ธ

Because hyper63โšก is modular and in this case using express, you can use any express framework middleware to manage your authentication process, you can add scopes and and more advanced security checks for each endpoint.

For example, let's say you only wanted certain clients to be able to create and delete datastores.

You would modify your JWT to perform special checks based on those endpoints.

JS
|

Need specific help? You can always reach out to our support team for any additional assistance at checkout our help desk๏ปฟ

Updated 15 Mar 2022
Did this page help you?
Yes
No
UP NEXT
Configuration
Docs powered byย archbeeย 
TABLE OF CONTENTS
Default๐Ÿš€
Custom ๐Ÿ› ๏ธ