Saravanan666/pypi-org huggingface dataset:
Package: httpie-esni-auth
# ESNI Auth Plugin for HTTPieAn [HTTPie](https://httpie.org/) auth plugin to support ESNI (aka SCTE-224) request signing. This allows you to use the `http` utility to easily make signed requests against a compliant server which checks for request signatures.## UsageFirst, install HTTPie and the plugin:```sh# By default on Mac, you'll need to grab `pip` first. This is a one-time task# you run on a new Mac then immediately forget about!sudo easy_install pip# Now install HTTPie and our pluginsudo pip install httpie httpie-esni-auth```Then you can start making requests!```sh# Local testing against an example ESNI Service on port 8080http -A esni -a 'user:pass' post :8080/example/audience/test# Set an old date header that should failhttp -A esni -a 'user:pass' post :8080/example/audience/test Date:'Mon, 16 Mar 2015 22:32:15 GMT'# Upload file to a production hosthttp -A esni -a 'user:pass' post https://example.com/example/audience/test Content-Type:application/xml <audience.xml```### OptionsIn order to see the request going out, use the standard `-v` option to HTTPie. Aside from that, there are some configurable values you can set in environment variables:Name              | Description----------------- | -----------VERBOSE           | Extra output from the signer, if setESNI_SCOPE        | Sets the auth scope, default is `esni`ESNI_SERVICE_NAME | Sets the service name, default is `esni`Example:```shVERBOSE=1 http -A esni -a 'user:pass' post :8080/...```## LicenseCopyright 2017 iStreamPlanet Co., LLCLicensed under the Apache License, Version 2.0 (the "License");you may not use this file except in compliance with the License.
Package: httpie-firebase-auth
HTTPie Firebase Auth PluginThis project provides an authentication plugin forHTTPiethat allows you to authenticate requests
using bearer tokens fromFirebase Auth.InstalationThe plugin can be installed with PIP.pip3install--userhttpie-firebase-authOnce installed, you should see the optionfirebaseunder--auth-typeinhttp --helpoutput. The--authargument then accepts a username, password, and an optional project ID (username:password[:project-id]). If the
project ID is passed in theauthargument, it takes priority over the configuration file (outlined below).# with username and passwordhttps--auth-type=firebase-auser@gmail.com:p@ssw0rdapi.example.com# with username and password and project IDhttps--auth-type=firebase-auser@gmail.com:p@ssw0rd:my-project-idapi.example.comConfigurationThere are several steps to perform before the plugin can add authentication details to HTTP requests.ProjectsAll project configuration happens in${HTTPIE_CONFIG}/firebase/projects.json. There is a section forkeysthat map a
project ID with an API key from the Firebase console. This key is the public web API key for the project.NOTE:The project IDs do not need to match the project ID on Firebase.Endpoint mappingThe plugin allows HTTPie to determine the correct Firebase project to use to authenticate a given request. This means
that you can use different Firebase Auth projects for different endpoints. The endpoint section maps a project ID to a
list of hostname globs. There are two wildcard characters (*and?) for matching multiple characters or a single
character respectively. A default project can be specified as a fallback if none of the endpoints match.Example configuration file{"default":"project-1","keys":{"project-1":"AIz....","project-2":"AIz...."},"endpoints":[{"project":"project-1","hosts":["localhost","api.example.com","*.example.io"]},{"project":"project-2","hosts":["prod.example.com"]}]}Credential CachingWhen a user is successfully authenticated against a Firebase project, the ID token and refresh token are cached in a
project specific file. On subsequent requests, if the provided email address is found in the project cache, the previous
ID token is used if it has not expired. If the token has expired, the refresh token is used to retrieve a new ID token.
The updated tokens are then stored in teh cache.When combined withHTTPie sessions, the plugin is able to
continue to authenticate requests for the user until the refresh token is no longer valid or revoked.TODODocument theconfig.jsonHow to add a project to api-key mappingStructure for configuring which api-key/project is used for a set of hostsAdd more details to the config specDocument credentials cache more completely
Package: httpie-gssapi
GSSAPI authentication plug-in forHTTPie.This plug-in uses therequests-gssapilibrary, which is a more-modern replacement of the oldrequests-kerberoslibrary.Installation$pipinstallhttpie-gssapiThis will add thegssapiauthentication method under--auth-typein the$ http--helpoutput.UsageEnsure you have a valid Kerberos token by runningkinit.$http--auth-type=gssapihttps://example.orgNote that supplying authentication credentials is not necessary, meaning the following two
commands are equivalent:$http--auth-type=gssapihttps://example.org$http--auth-type=gssapi--auth:https://example.orgConfiguration OptionsThe following environment variables can be set to modify the GSSAPI authentication behavior:HTTPIE_GSSAPI_MUTUAL_AUTH(default:required): determines whether mutual authentication
from the server should be required. For more information, seeMutual Authentication. Possible values are:required,optional,disabled.HTTPIE_GSSAPI_OPPORTUNISTIC_AUTH(default:no): enables or disables preemptively
initiating the GSSAPI exchange. For more information, seeOpportunistic Authentication. Possible
values are:yes,true,1; all other values default tono.HTTPIE_GSSAPI_DELEGATE(default:no): enables or disables credential delegation. For
more information, seeDelegation.
Possible values are:yes,true,1; all other values default tono.
Package: httpie-hmac-auth
HMACauth plugin forHTTPie.HTTP requests will be signed with a shared secret key using HMAC. The string to sign format is:<Method>\n<Content-MD5>\n<Content-Type>\n<Date>\n<URL>Example String-to-signPOSTvVqHE1k/uBRCoWe0FAh95g==application/jsonTue,12Jan201614:57:28GMT/api/v1/avatarsExample Authorization Header with HMAC signatureAuthorization:HMACXH+v0qhV4i/89y/DT2OOJx9Kjf3f/0j+w2aGZk625nU=Installation$pipinstallhttpie-hmac-authYou should now seehmacunder--auth-typein$ http--helpoutput.Usage$http--auth-type=hmac--auth='client:secret'example.orgExamplesTo authenticate a client request when an access key is required by the server to lookup the shared secret:$http--auth-type=hmac--auth="client:secret"example.orgTo authenticate a client request when there is no requirement for a client to supply an access key:$http--auth-type=hmac--auth=":secret"example.orgLicenseCopyright (c) 2016 The Guardian. Available under the MIT License.
Package: httpie-keystone-auth
OpenStack Keystone auth plugin forHTTPie.Installation$pipinstall--upgradehttpie-keystone-authYou should now seekeystoneunder--auth-type/-Ain$ http--helpoutput.UsagePlugin usesopenstacksdklibrary to parse theclouds.yamlfile and
get the token from Keystone.A simple example of aclouds.yamlfile is:clouds:mycloud:auth:auth_url:<url of keystone endpoint>username:<username>password:<password>user_domain_name:<user domain name>project_name:<name of the project to authorize to>project_domain_name:<domain of the project>othercloud:auth:. . .Read more about the format of the file and where to place it inopenstacksdk docsUsing env varYou can setOS_CLOUDenv var to a name of one of the clouds in theclouds.yamlfile, which will be then used by plugin:exportOS_CLOUD=mycloudhttp-Akeystonedevstack.local/images/v2/imagesPassing cloud name explicitlyAlternatively you can pass the name of the cloud from theclouds.yamlfile
to use as ‘username’ to HTTPie:https-Akeystone-amyothercloudimages.othercloud.com/v2/imagesUsing service type instead of full service URLThis plugin also simplifies working with OpenStack APIs by allowing you
to specify only theservice typeinstead of full URL, e.ghttps-Akeystonecompute/serversUnder the hood, the plugin will check if there’s any service in the OpenStack
service catalog of your cloud that has the service type as specified in the
first part (netloc) of your URL, and replace this with the endpoint
URL for this service as defined in the catalog for the region and endpoint type
(interface) as set in yourclouds.yaml. It will use API version as defined
in theclouds.yamlfile andopenstacksdkdefaults.Additionally, instead of service type that is actually registered
in the service catalog of the cloud, you can also use any of:official service type (likeblock-storage)official service type alias (likevolumev3)OpenStack community project name (likecinder)service name as registered in the catalog (can be whatever cloud operator
decided to name it)If a single endpoint matching such criteria is found, it will be used.OpenStack API microversionsSeveral OpenStack services use API microversions to alter the API behavior.
The actual header is pretty long and cumbersome to type, and it can vary
for some older versions of some services.Instead, you can specify a simple headerv, and appropriate microversion
header will be included, together with legacy ones if required, e.g.https-Akeystonecompute/serversv:2.59-vGET/v2.1/serversHTTP/1.1...OpenStack-API-Version:compute2.59# modern API microversion headerX-OpenStack-Nova-API-Version:2.59# legacy API microversion header...Note that this only works when using a service type etc instead of full URL.LimitationsIf you are using cloud that needs custom CA bundle file to verify the TLS
connection, you will still have to pass it explicitly to HTTPie
even if it is already set in theclouds.yamlfile.
Package: httpie-kong-hmac
httpie-kong-hmacHMAC auth plugin forHTTPieandKongIt currently provides support for Kong HmacInstallation$pipinstallhttpie-kong-hmacUsage$http--auth-type=kong-hmac--auth='client-key:client-secret'example.orgYou can also useHTTPie sessions:# Create session$http--session=logged-in--auth-type=kong-hmac--auth='client-key:client-secret'example.org# Re-use auth$http--session=logged-inPOSTexample.orghello=worldIf you userequests:fromhttpie_kong_hmacimportKongHMACimportrequestsresp=requests.get('http://example.org',auth=KongHMAC('client-key','client-secret'),)print(resp.status_code,resp.content)
Package: httpie-kws
KWS app auth plugin for httpieUsing command line argumentshttps-Akws-u$appid:$appsecrethttps://kws.knd.com.cn/api/v4/manufacturers/Using environment variablesexportKWS_APP_ID=$appidexportKWS_APP_SECRET=$appsecrethttps-Akwshttps://kws.knd.com.cn/api/v4/manufacturers/Using configuration fileDownload app auth file to$HOME/.kws-authhttps-Akwshttps://kws.knd.com.cn/api/v4/manufacturers/
Package: httpie-lambda
Invoke AWS Lambda from the command line with all the convenience ofHTTPieand without
having to utilize API Gateway.Quick StartInstallationpipintallhttpie-lambdaUsageUsage is consistent with HTTPie, simply usehttp+lambdaas protocol and the name of the lambda as host portion of the URL.To callhealthendpoint of the Lambda function namedflaskexp-test:>httphttp+lambda://flaskexp-test/healthHTTP/1.1200OKContent-Length:21Content-Type:application/jsonX-Request-ID:{"status":"UP"}For more comprehensive example such as POST refer toHTTPie usagedocumentation.Specify a region or AWS credentials profile:>envAWS_DEFAULT_REGION=us-west-2AWS_PROFILE=sukhanovhttphttp+lambda://flaskexp-test/healthHTTP/1.1200OKContent-Length:21Content-Type:application/jsonX-Request-ID:{"status":"UP"}For more information on AWS Authentication configuration seelambda-requests.How does its workLambda is invoked with payload that emulates AWS API Gateway simple proxy format. This enables calling of lambda as an HTTP service without having to utilize AWS API Gateway itself.
Package: httpie-llnw-auth
httpie-llnw-authThis module provides an authentication plugin for HTTPie to generate the X-LLNW-Security-* request headers required by Limelight Networks APIs.Getting StartedFirstly, install the package:pip install httpie-llnw-authThen:# Simplest example, if LLNW_API_USERNAME and LLNW_API_KEY environment variables are sethttp-Allnwhttps://apis.llnw.com/config-api/v1/svcinst/delivery/shortname/<yourshortname># Providing API user and key inline (be careful since this will add your API key to your shell history)http-Allnw-a"myuser:myapikey"https://apis.llnw.com/config-api/v1/svcinst/delivery/shortname/<yourshortname># Providing API user inline, and interactively prompting for API keyhttp-Allnw-amyuserhttps://apis.llnw.com/config-api/v1/svcinst/delivery/shortname/<yourshortname>
Package: httpie-mauth
HTTPie mauthThis is a plugin for theHTTPiecommand line request library that allows it to send mauth-authenticated requests.To use this, you will need:A MAuth App IDA MAuth private key whose corresponding public key is registered with the
MAuth server that the target service is usingA MAuth config file in a supported location, one of:~/.mauth_config.yml./config/mauth.yml./mauth.ymlThe format of that file should be as follows:development:app_uuid:a36c9238-c9c8-4de9-a385-07dfe6dc1fc4private_key_file:/Users/mgup/.mauth_keyYou can then issue signed requests as follows:http --auth-type mauth https://example.comYou can pass the-voption to see the outgoing header. Validating the
signature of the response is not currently supported.
Package: httpie-media-auth
httpie-media-authBce Multimedia auth plugin for HTTPie.Installation$ pip install –upgrade httpie-media-authUsageCredentials on the CLIThe syntax and behavior is the same as with the basic auth.Specify both access key ID and secrethttp –auth-type media -a ACCESSKEYXXX:SECRETKEYXXX http://localhost:80/test
Specify only the keyThere’ll be a password prompt:$ http -A media -a ACCESSKEYXXXhttp://localhost:80/testhttp: password forACCESSKEYXXX@localhost: <enter secret key>
Auth via the Media_* environment variables
Package: httpie-negotiate
SPNEGO (GSS Negotiate) auth plugin forHTTPie, based on Jakub’s httpie-ntlm example.Installation$pipinstallhttpie-negotiateYou should now seenegotiateunder--auth-typein$ http--helpoutput.UsageYou need to have a valid Kerberos principal, run kinit first if necessary.$http--auth-type=negotiate--auth:https://example.orgKerberos mutual authentication is REQUIRED by default and is recommended.
If you strictly require mutual authentication to be OPTIONAL or DISBALED, then you can use theHTTPIE_KERBEROS_MUTUALenvironment variable.$HTTPIE_KERBEROS_MUTUAL=OPTIONALhttp--auth-type=negotiate--auth:https://example.org$HTTPIE_KERBEORS_MUTUAL=DISABLEDhttp--auth-type=negotiate--auth:https://example.orgYou can also useHTTPie sessions:# Create session$http--session=logged-in--auth-type=negotiate--auth:https://example.org# Re-use auth$http--session=logged-inPOSThttps://example.orghello=world
Package: httpie-next
HTTPie Extra!This plugin brings support for HTTP/2 and HTTP/3 to HTTPie.
Use this plugin with caution as it uses urllib3.future (and actually shadows urllib3 in your environment).pipinstallgit+https://github.com/Ousret/httpie-next-U# run twice! first is http/2 and second should be http/3httpsGETwww.cloudflare.com/img/nav/globe-lang-select-dark.svgWhen a server yield its QUIC support, it is saved in the default HTTPie configuration directory.
Installing this in your environment will alter basically everything that relies on urllib3.Your feedback is appreciated so that we can prepare a safe (and actually reviewable / merge-able feature) in urllib3.
Package: httpie-nifcloud-authv4
AWS/NIFCLOUD Auth v4 plugin for HTTPieDescriptionHTTPieで AWS / NIFCLOUD Signature v4
の認証をリクエストに付加するための Auth plugin です。Installpipinstall--upgradehttpie-nifcloud-authv4github masterからinstallする場合:pipinstall--upgradegit+https://github.com/kzmake/httpie-nifcloud-authv4Preparation-Anifcloudの場合、 1.-a...で指定されたACCESS_KEY_ID / SECRET_ACCESS_KEY1. 環境変数NIFCLOUD_ACCESS_KEY_ID / NIFCLOUD_SECRET_ACCESS_KEY2. 環境変数ACCESS_KEY_ID / SECRET_ACCESS_KEYの順で適用されます。環境変数 ACCESS_KEY_ID / SECRET_ACCESS_KEY を用いてリクエストする場合for bash / zshexportACCESS_KEY_ID={払い出されたACCESS_KEY_ID}exportSECRET_ACCESS_KEY={払い出されたSECRET_ACCESS_KEY}for fishset-gx ACCESS_KEY_ID{払い出されたACCESS_KEY_ID}set-gx SECRET_ACCESS_KEY{払い出されたSECRET_ACCESS_KEY}ACCESS_KEY_ID / SECRET_ACCESS_KEY を設定後、リクエストしてください。リクエストに直接 ACCESS_KEY_ID / SECRET_ACCESS_KEY を指定してリクエストする場合http-v-Anifcloud-a{払い出されたACCESS_KEY_ID}:{払い出されたSECRET_ACCESS_KEY}https://jp-east-1.hatoba.api.nifcloud.com/v1/clusters上記のコマンドのように-a{払い出されたACCESS_KEY_ID}:{払い出されたSECRET_ACCESS_KEY}を追加してリクエストしてください。Usage-Anifcloudを HTTPie に追加し、リクエストしてください。利用可能な引数の形式-a...で認証情報を指定することが可能です。...に指定可能な形式は以下となります。{region_name}/{service_id}{ACCESS_KEY_ID}:{SECRET_ACCESS_KEY}{ACCESS_KEY_ID}:{SECRET_ACCESS_KEY}:{region_name}/{service_id}{ACCESS_KEY_ID}:{SECRET_ACCESS_KEY}:{region_name}:{service_id}{region_name}.{service_name}.api.nifcloud.com の場合オブジェクトストレージHatoba（β）NASRDB{region_name}/{service_id}に.が含まれない場合、自動でregion_name/service_idを読み取りリクエストします。
または、-a{region_name}/{service_id}と指定し、リクエストしてください。http-v-Anifcloud-a{払い出されたACCESS_KEY_ID}:{払い出されたSECRET_ACCESS_KEY}https://jp-east-1.hatoba.api.nifcloud.com/v1/clustershttp-v-Anifcloud-a{払い出されたACCESS_KEY_ID}:{払い出されたSECRET_ACCESS_KEY}:jp-east-1/hatobahttps://jp-east-1.hatoba.api.nifcloud.com/v1/clustershttp-v-Anifcloud-ajp-east-1/hatobahttps://jp-east-1.hatoba.api.nifcloud.com/v1/clusters{service_name}.api.nifcloud.com の場合ESSスクリプト-a/{service_id}と指定し、リクエストしてください。http-v-f-Anifcloud-a{払い出されたACCESS_KEY_ID}:{払い出されたSECRET_ACCESS_KEY}:east-1/emailhttps://ess.api.nifcloud.com/Action=ListIdentitiesVersion=2010-12-01http-v-f-Anifcloud-aeast-1/emailhttps://ess.api.nifcloud.com/Action=ListIdentitiesVersion=2010-12-01GET の例Query (Action==ListIdentitiesVersion=2010-12-01)
を指定してリクエストしてください。http-v-Anifcloud-a{払い出されたACCESS_KEY_ID}:{払い出されたSECRET_ACCESS_KEY}:east-1/emailhttps://ess.api.nifcloud.com/Action==ListIdentitiesVersion==2010-12-01POST の例Formオプション(-f) を指定し、 Form data
(Action=ListIdentitiesVersion=2010-12-01)
を指定してリクエストしてください。http-v-f-Anifcloud-a{払い出されたACCESS_KEY_ID}:{払い出されたSECRET_ACCESS_KEY}:east-1/emailhttps://ess.api.nifcloud.com/Action=ListIdentitiesVersion=2010-12-01raw-payload("Action=ListIdentities&Version=2010-12-01")
をパイプで渡してリクエストする場合は以下のようになります。printf"Action=ListIdentities&Version=2010-12-01"|http-v-f-Anifcloud-aeast-1/emailhttps://ess.api.nifcloud.com/echo"Action=ListIdentities&Version=2010-12-01"|tr-d'\n'|http-v-f-Anifcloud-aeast-1/emailhttps://ess.api.nifcloud.com/
Package: httpie-nsof
Nsof OAuth 2 plugin for theHTTPiecommand line HTTP client.Installation$pipinstallhttpie-nsofYou should now seensofunder--auth-typein$ http--helpoutput.Setup$httpie-nsof-setupConfigure Nsof’s auth plugin with your creds (saved in ~/.httpie/config.json).
The credentials can be either a username/password or API Key ID/API Key SecretNotes:if username is not provided in conf file it will be searched at HTTPIE_NSOF_USERNAMEif password is not provided in conf file it will be searched at HTTPIE_NSOF_PASSWORDmanually inputted username/password supersede conf file and environment variablesUsage$http--auth-type=nsofGEThttps://api.nsof.io/v1/usersIt’s possible to pass a different effective org using the envEORG:$EORG=nsofhttp--auth-type=nsofGEThttps://api.nsof.io/v1/users
Package: httpie-ntlm
NTLM auth plugin forHTTPie.Installation$pipinstallhttpie-ntlmYou should now seentlmunder--auth-typein$ http--helpoutput.Usage$http--auth-type=ntlm--auth='domain\\username:password'example.orgYou can also useHTTPie sessions:# Create session$http--session=logged-in--auth-type=ntlm--auth='domain\\username:password'example.org# Re-use auth$http--session=logged-inPOSTexample.orghello=world
Package: httpie-oauth
httpie-oauth===========OAuth plugin for `HTTPie <https://github.com/jkbr/httpie>`_.It currently provides support for OAuth 1.0a 2-legged.Installation------------.. code-block:: bash$ pip install httpie-authYou should now see ``oauth1`` under ``--auth-type`` in ``$ http --help`` output.Usage-----.. code-block:: bash$ http --auth-type=oauth1 --auth='client-key:client-secret' example.orgYou can also use `HTTPie sessions <https://github.com/jkbr/httpie#sessions>`_:.. code-block:: bash# Create session$ http --session=logged-in --auth-type=oauth1 --auth='client-key:client-secret' example.org# Re-use auth$ http --session=logged-in POST example.org hello=world
Package: httpie-plex
Plex OAuth2 Plugin forHTTPie.Installation$pipinstallhttpie-plexYou should now seeplexunder--auth-typein$ http--helpoutput.HomebrewIf you’ve installed HTTPie using Homebrew, but it’s pointing to your system Python,
there may be other hoops to jump through. Note that this doesn’t apply if you’ve
also installed Python via Homebrew: essentially, ifpip listlistshttpie,
you’re good to go with the method above. Otherwise, you’ll need to manually
install it into the proper directory. First, clone the repository.
You’ll then need to figure out which version of HTTPie you have installed.
Then do something like:$PYTHONPATH="/usr/local/Cellar/httpie/0.9.8/libexec/lib/python2.7/site-packages:/usr/local/Cellar/httpie/0.9.8/libexec/vendor/lib/python2.7/site-packages"\pythonsetup.pyinstall\--prefix=/usr/local/Cellar/httpie/0.9.8/libexec/vendorUsage$http--auth-type=plex\--auth='client_id:client_secret'\https://apibase.com/consumersToken StorageTo cache the OAuth2 token, this package uses a folderplexinside theHTTPie config directory.
This defaults to, on *nix machines,~/.httpie/plex. You can set a different base directory by setting theHTTPIE_CONFIG_DIRenvironment variable.Testing and ContributingTests are run with$pythonsetup.pytestContributions are welcome! For new features, tests are a requirement and should
have good coverage. For bug fixes/improvements, tests must pass. Further, code
must be style-checked withpycodestyle.
Package: httpie-signature
An Http Signature Authentication plugin forHTTPie <https://httpie.io>.HTTP Signatures describe a method of creating, encoding and verifying a signature within an HTTP request
Http     Signature Authentication is described in the following working documenthttps://tools.ietf.org/id/draft-cavage-http-signatures-12.htmlHow to install$pipinstallhttpie-signatureHow to use$https--auth-type=signaturehttps://apitest.cybersource.com/pts/v2/payments'v-c-merchant-id: test'~/.httpsigrc fileFormat:[URL]key=<key>secret=<secret>headers=<Stringvalueofheadersusedinsignatur>Sample ~/.httpsigrc file[mywebsite.com]key=e3e0e662-0187-49d3-b4ba-09dcf4649a91secret=EcLO2Ybb7ChSLeQsAIPqEBnJpAm1Y3ypw2b4n4RqWnw=algorithm=HmacSHA256headers=hostdate(request-target)digest[anotherwebsite.com]key=51da5b74-34b9-4dc0-9330-3fc4e9fbac03secret=ASDOASFKAFasd3rtsfasfWZFAFDWTRWFSGDFSDsds35=algorithm=HmacSHA256headers=hostdate(request-target)digestIf your request does not contain a body digest will automatically be removed from the header list.
Package: httpie-snapdsocket
Snapis an app store for Linux.
Snapd is the custom URL protocol used to talk to that store using theirREST API.Installation$python-mpipinstall--upgradehttpie-snapdsocketExample usageTo queryhttpieSnap package details:$http'snapd:///v2/find?name=httpie'Have a look at theSnapd REST API documentationfor more information.Requirementsrequests-unixsocketCreditsBased on the original code from @chipaca (chipaca/httpie-snap).
Package: httpie-visionect-auth
HMAC for JoanAssistantauth plugin forHTTPie.HTTP requests will be signed with a shared secret key using HMAC. Differs from AWS or other HMAC strings because: JoanAssistant
The string to sign format is:<Method>\n\n<Content-Type>\n<Date>\n<URL>Example String-to-signGETapplication/jsonSun,18Jun201711:48:26GMT/api/device/Example Authorization Header with HMAC signatureAuthorization:1b9dbaf5b1183037:Mx0Qi57rqYIbc4gDiDKqYERK8Vmzdwhqk3S+OYoXRu0=Installation$pipinstallhttpie-visionect-authYou should now seevisionectunder--auth-typein$ http--helpoutput.Usage$http-j--auth-type=visionect--auth='client:secret'server:8081/api/users/ExamplesTo request status on all registered Joan Devices$http-j--auth-type=visionect--auth="client:secret"server:8081/api/devices/LicenseCopyright (c) 2017 Pierre. Available under the MIT License.