uncleflo
Registered since September 28th, 2017
Has a total of 4281 bookmarks.
Showing top Tags within 4 bookmarks
howto information development guide reference administration design website software solution online service product business uk tool company linux code server application system web list video marine create data experience tutorial description explanation learn technology build article blog world project boat download windows lookup security free performance javascript technical london beautiful control network tools support course file research purchase image library programming youtube example php construction install opensource community html quality computer feature profile power browser music platform process mobile work user share manage professional database hardware buy industry advice internet dance developer installation search 3d camera customer access travel material standard money test develop documentation review css engineering photography webdesign engine device digital speed event api source management question program client phone discussion content simple story water marketing yacht app account setup interface package idea fast communication compare cheap script market study easy live google resource operation demonstration contact startup
Tag selected: authorization.
Looking up authorization tag. Showing 4 results. Clear
JSON Web Token Introduction - jwt.io
Saved by uncleflo on April 10th, 2021.
JSON Web Token (JWT) is an open standard (RFC 7519) that defines a compact and self-contained way for securely transmitting information between parties as a JSON object. This information can be verified and trusted because it is digitally signed. JWTs can be signed using a secret (with the HMAC algorithm) or a public/private key pair using RSA or ECDSA. Although JWTs can be encrypted to also provide secrecy between parties, we will focus on signed tokens. Signed tokens can verify the integrity of the claims contained within it, while encrypted tokens hide those claims from other parties. When tokens are signed using public/private key pairs, the signature also certifies that only the party holding the private key is the one that signed it.
token secure header verify authorization authentication credentials apis schema signature algorithm user browser resistant secret standard transmit information json object hmac key integrity web introduction development administration api check identity
Brandfolder API V4
Saved by uncleflo on April 3rd, 2021.
This is a living document, intended to help you enjoy working with Brandfolder's API. V4 is a RESTful JSON API giving you programmatic access to the same resources you can access as a user of our website. You're probably wondering, "Which resources are those?"
Well each one has its own section in this documentation for you to learn in more detail exactly what operations you can perform in relation to that particular resource, but a bit of an overview here might be helpful. As a Brandfolder user, you are part of one or more Organizations. Organizations can have multiple Brandfolders. Brandfolders have Sections which hold Assets. Assets have Attachments and can also have Tags and Custom Fields.
fetchforpets endpoint clipboard restful request parameter authentication documentation invitation authorization images cdn content storage api internet resource system tool development code curl
The OAuth 2.0 Authorization Framework
Saved by uncleflo on July 10th, 2017.
The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 1.0 protocol described in RFC 5849.
authorization framework oauth resource interaction authentication standardization standard description rfc specification development administration protocol approval access document
ESTA - Welcome to the Electronic System for Travel Authorization
Saved by uncleflo on January 22nd, 2013.
International travelers who are seeking to travel to the United States under the Visa Waiver Program (VWP) are now subject to enhanced security requirements and will be required to pay an administrative fee. All eligible travelers who wish to travel to the U.S. under the Visa Waiver Program must apply for authorization and then pay the fee using the following process. Please refer to the Help link at the top of each Web page if you have questions. Before you begin this application, make sure that you have a valid passport and credit card available. This application will only accept the following credit cards: MasterCard, VISA, American Express, and Discover (JCB, Diners Club).
esta electronic system travel authorization secure border america usa policy waiver homeland security
No further bookmarks found.