Check specific patterns on git-cached files.
AWS SDK for JavaScript Secrets Manager Client for Node.js, Browser and React Native
Azure Key Vault Secrets
An eslint rule that searches for potential secrets/keys in code
OCI NodeJS client for Secrets Service
Secretlint CLI that scan secret/credential data.
Credential management facilities for Imperative, Zowe CLI, and extenders.
Secrets Manager middleware for the middy framework
React hooks and UI for reading and managing secrets in a Sanity Studio. This is a good pattern for keeping configuration secret. Instead of using environment variables which would be bundled with the Studio source (it is an SPA), we store secret informati
The parameters package for the Powertools for AWS Lambda (TypeScript) library
The 1Password JavaScript SDK offers programmatic read access to your secrets in 1Password in an interface native to JavaScript. The SDK currently supports `Node.JS`
Node.js wrapper for dash-licenses, that makes it easier to perform license checks for JS/TS Eclipse Foundation projects
RFC 4226 HOTP implementation for otplib
secrets-mgr plugin
Common internal functionality for all of the Azure Key Vault clients in the Azure SDK for JavaScript
RFC 6238 TOTP implementation for otplib
Abstraction around [AWS Systems Manager](https://docs.aws.amazon.com/systems-manager/latest/userguide/what-is-systems-manager.html) (SSM) for CRUDL options on SSM SecureString values. This package should be used whenever we want to read/write secrets to S
Expose config variables to React Native apps
Keeper Secrets Manager Javascript SDK
Refer to the [SDK documentation](https://docs.bucketeer.io/sdk/client-side/javascript) for instructions on how to use the SDK.
NodeJS SDK for Pulumi ESC
A developer-friendly secrets detection tool for CI and pre-commit hooks based on Yelp's detect-secrets
CubeSigner SDK session manager backed by AWS Secrets Manager
Azure key-vault flex volume to express properties integration
Checks integrity of Yandex.Money payment notification by comparing SHA of strigified params including a secret shared with Yandex.
Check if YAML files contain secrets that should be in ENV
This module provides common interface to HMAC functionality. HMAC is a kind of "Message Authentication Code" (MAC) algorithm whose standard is documented in RFC2104. Namely, a MAC provides a way to check the integrity of information transmitted over or stored in an unreliable medium, based on a secret key. Originally written by Daiki Ueno. Converted to a RubyGem by Geoffrey Grosenbach
A MAC provides a way to check the integrity of information transmitted over or stored in an unreliable medium, based on a secret key.
A MAC provides a way to check the integrity of information transmitted over or stored in an unreliable medium, based on a secret key.
A MAC provides a way to check the integrity of information transmitted over or stored in an unreliable medium, based on a secret key.
Keep secrets in your config files. Valvet encrypts sensitive values while leaving everything else readable, so you can check the whole file into version control. Uses NaCl sealed boxes via RbNaCl.
This is a gem originated from another gem called permalink. Since I often want a permalink that provides no way to tell the database ids, I came up with the idea about encrypting the id and prepending it to the permalink. For more information about FPE(Format Preserving Encryption), please consult the wikipedia. The encryption method of current release is simply RC4-40 with a configurable key. Note, RC4-40 is not a strong encryption algorithm at all, and you shouldn't rely on it to delivery sensitive information. Also, to prevent inconsistance of encryption, and duplication(although the chance is very low) you should keep your key as a secret and never change it. The original implementation of generating permalink involves a infite loop to check uniqueness in database. It's slow, inefficient and most importantly, it still can't prevent race condition. And since we are using a FPE algorithm on the database id, which is garanteed to be unique from database, we don't need to put ourselves in that inefficient loop. Finally, what's the purpose of this gem? It's only a gem that helps hiding your database ids.
# Fresh::Auth This gem makes it really, REALLY easy to use the Freshbooks API. It couldn't be easier. With only 3 functions you'll ever need to use, and only 2 required configuration values, it can't get any easier. ## Installation Add this line to your application's Gemfile: gem 'fresh-auth' And then execute: $ bundle Or install it yourself as: $ gem install fresh-auth ## Usage ### Configuration: You must define your Freshbooks subdomain and your OAuth Secret in your application code before using Fresh::Auth. For Ruby on Rails apps, a new file at config/initializers/fresh-auth.rb would be appropriate. Your configuration file should look like this (you fill in the three empty strings): Fresh::Auth.configure do |config| # The part of your login url between 'http://' and '.freshbooks.com' config.url.subdomain = "" # Under 'My Account' (on the top right when you're logged into Freshbooks) # -> 'Freshbooks API' -> 'OAuth Developer Access' -> 'OAuth Secret' # You'll need to request this from Freshbooks initially. config.oauth_secret = "" # Optional. Any string of your choice. Be creative or check out http://www.thebitmill.com/tools/password.html config.nonce_salt = "" end Fear not: If you try to use Fresh::Auth without configuring it first, an exception will be thrown that clearly describes the problem. ### Public API: There are two modules in this API: Fresh::Auth::Authentication and Fresh::Auth::Api #### Fresh::Auth::Authentication This module authenticates you with Freshbooks, storing the authentication in an array called `session`. This integrates seamlessly with Ruby on Rails' controller environment. If you're using some framework other than Ruby on Rails, make sure to define session in your class before including the Authentication module. This isn't recommended because your class will also need to define other objects called `params` and `request` and implement a `redirect_to` method. It gets complicated. Better leave it to Rails to handle this for you. The only public function of this module is AuthenticateWithFreshbooks. To use it, just add the following line of code to your controller: ` include Fresh::Auth::Authentication ` Then, the following line of code authenticates with Freshbooks from any method in your controller: ` AuthenticateWithFreshbooks() ` Note that, after authenticating with Freshbooks, the user will be redirected back to the same path using HTTP GET, so make sure the resource supports HTTP GET and that in the business logic executed on GET, AuthenticateWihFreshbooks() is called. #### Fresh::Auth::Api Once you've authenticated, you want to send XML requests to Freshbooks. The first step is preparing the XML with Fresh::Auth::Api.GenerateXml, which you'll supply with a block that defines all the nested XML that you want in your request. GenerateXml also takes two arguments before the block: the class and method that you want to call. First, in your controller: `include Fresh::Auth::Api` Then, in some method in that controller: my_xml = GenerateXml :invoice, :update do |xml| xml.client_id 20 xml.status 'sent' xml.notes 'Pick up the car by 5' xml.terms 'Cash only' xml.lines { xml.line { xml.name 'catalytic converter' xml.quantity 1 xml.unit_cost 450 xml.type 'Item' } xml.line { xml.name 'labor' xml.quantity 1 xml.unit_cost 60 xml.type 'Time' } } end Ok, you created the XML. Now you want to send it. Sounds pretty complicated, right? Not at all! Ready? Let's go! `_response = PostToFreshbooksApi my_xml` Now, are you wondering what's in `_response`? I'll tell you shortly, but before we discuss that, we have to know about the exception that PostToFreshbooksApi might raise. It raises a detailed error message if the response status is not 'ok'. Makes sense, right? Now, you still want to know what's in `_response`? Oh, nothing fancy. Just a Nokogiri XML object, representing the root element of the xml response. Could this get any easier? ## Contributing 1. Fork it 2. Create your feature branch (`git checkout -b my-new-feature`) 3. Commit your changes (`git commit -am 'Added some feature'`) 4. Push to the branch (`git push origin my-new-feature`) 5. Create new Pull Request