conjur-api 6.0.1.pre.523 → 6.0.1.pre.562

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 0ec9d0ed0952ec93fd6453d09675def952e8643ff06622a25d234a3eb21b6cee
-  data.tar.gz: a2a4636dab90dc006cdc54f074bf3ea7a9d606def2d499e3d151ebf8a58a94ad
+  metadata.gz: 741fa8ac938000520f64d873f27ba567105da559f7009894b2a6d29a1bdbc1de
+  data.tar.gz: 68bcdf0e71536d2a0e232739c5c56d59fcfa5dc7b77ddd3177041d8c778ace9a
 SHA512:
-  metadata.gz: 5ce0eb70c19ab6cb02064d6ac8ae75c68fd98e045a3203068d209b3d69512152d34da7ff2f901870b16072a3fd3aecfca643f8278d3836fb4d5a04c9df46bfe1
-  data.tar.gz: c923c9fdb7671f0ff595ece0da54a8c850f988ab35acf672705c6dbcdc362026ed1196bbe5885219670d916f4b0e778d8ed84a05a93efdc26b8e7c8922c8cf9c
+  metadata.gz: 5205e6586150e59ee3f9436141361cd2e96a9edaf7f8df1f34c516a8f9d93dbab459ce2fc272991f439807107008c8cfb69574ef8c4b0720cae65d008db58412
+  data.tar.gz: 8626037bda7a60668e8a64e04787c1b1c3ae891e2f9abee64ac5550180c9f71a0993a31992bb6988bf24817dde321faee1e49dc7b9a435f2db09809332dda9c3

data/CHANGELOG.md

@@ -9,9 +9,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - Nothing should go in this section, please add to the latest unreleased version
   (and update the corresponding date), or add a new version.
 
-## [6.0.1] - 2024-03-25
+## [6.0.1] - 2025-09-05
 
 ### Fixed
+- Updated README.md, CONTRIBUTING.md, and SECURITY.md to align with Conjur Enterprise name change to Secrets Manager. (CNJR-10968)
 - Pass valid field in #memberships to fix listing roles (CNJR-2109)
 - Pull keycloak image from internal repository
 
@@ -395,7 +396,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 
 ## [2.0.0] - 2013-13-12
 
-[Unreleased]: https://github.com/cyberark/conjur-api-ruby/compare/v6.0.0...HEAD
+[Unreleased]: https://github.com/cyberark/conjur-api-ruby/compare/v6.0.1...HEAD
+[6.0.1]: https://github.com/cyberark/conjur-api-ruby/compare/v6.0.0...v6.0.1
 [6.0.0]: https://github.com/cyberark/conjur-api-ruby/compare/v5.4.1...v6.0.0
 [5.4.1]: https://github.com/cyberark/conjur-api-ruby/compare/v5.4.0...v5.4.1
 [5.4.0]: https://github.com/cyberark/conjur-api-ruby/compare/v5.3.7...v5.4.0

data/CONTRIBUTING.md

@@ -17,7 +17,7 @@ contributor!
 
 ## Development
 
-To develop and run tests against Conjur, use the `start` and `stop` scripts in the `dev` folder. The start script brings up an open source Conjur (and Postgres database), CLI container, and a "work" container, with the gem code mounted into the working directory.
+To develop and run tests against Conjur OSS, use the `start` and `stop` scripts in the `dev` folder. The start script brings up a Conjur OSS (and Postgres database), CLI container, and a "work" container, with the gem code mounted into the working directory.
 
 ### Starting a Shell
 

data/README.md

@@ -1,6 +1,6 @@
-# Conjur::API
+# CyberArk Secrets Manager API for Ruby
 
-Programmatic Ruby access to the Conjur API.
+Programmatic Ruby access to the Secrets Manager API.
 
 RDocs are available from the through the [Ruby Gem details page](https://rubygems.org/gems/conjur-api)
 
@@ -31,23 +31,20 @@ Or install it yourself as:
 
 # Usage
 
-Connecting to Conjur is a two-step process:
+Connecting to Secrets Manager is a two-step process:
 
-* **Configuration** Instruct the API where to find the Conjur endpoint and how to secure the connection.
+* **Configuration** Instruct the API where to find the Secrets Manager endpoint and how to secure the connection.
 * **Authentication** Provide the API with credentials that it can use to authenticate.
 
 ## Configuration
 
-The simplest way to configure the Conjur API is to use the configuration file stored on the machine.
-If you have configured the machine with [conjur init](http://developer.conjur.net/reference/tools/init.html),
+The simplest way to configure the Secrets Manager API is to use the configuration file stored on the machine.
+If you have configured the machine with [Secrets Manager CLI](https://github.com/cyberark/conjur-cli-go),
 its default location is `~/.conjurrc`.
 
-The Conjur configuration process also checks `/etc/conjur.conf` for global settings. This is typically used
-in server environments.
-
 For custom scenarios, the location of the file can be overridden using the `CONJURRC` environment variable.
 
-You can load the Conjur configuration file using the following Ruby code:
+You can load the Secrets Manager configuration file using the following Ruby code:
 
 ```ruby
 require 'conjur/cli'
@@ -55,18 +52,15 @@ Conjur::Config.load
 Conjur::Config.apply
 ```
 
-**Note** this code requires the [conjur-cli](https://github.com/conjurinc/cli-ruby) gem, which should also be in your
-gemset or bundle.
-
 ## Authentication
 
-Once Conjur is configured, the connection can be established like this:
+Once Secrets Manager is configured, the connection can be established like this:
 
 ```
 conjur = Conjur::Authn.connect nil, noask: true
 ```
 
-To [authenticate](http://developer.conjur.net/reference/services/authentication/authenticate.html), the API client must
+To authenticate, the API client must
 provide a `login` name and `api_key`. The `Conjur::Authn.connect` will attempt the following, in order:
 
 1. Look for `login` in environment variable `CONJUR_AUTHN_LOGIN`, and `api_key` in `CONJUR_AUTHN_API_KEY`
@@ -76,7 +70,7 @@ can be overridden using the configuration file `netrc_path` option.
 
 ## Connecting Without Files
 
-It's possible to configure and authenticate the Conjur connection without using any files, and without requiring
+It's possible to configure and authenticate the Secrets Manager connection without using any files, and without requiring
 the `conjur-cli` gem.
 
 To accomplish this, apply the configuration settings directly to the [Conjur::Configuration](https://github.com/conjurinc/api-ruby/blob/master/lib/conjur/configuration.rb)
@@ -99,20 +93,20 @@ In either case, you will also need to configure certificate trust. For example:
 OpenSSL::SSL::SSLContext::DEFAULT_CERT_STORE.add_file "/etc/conjur-yourorg.pem"
 ```
 
-Once Conjur is configured, you can create a new API client by providing a `login` and `api_key`:
+Once Secrets Manager is configured, you can create a new API client by providing a `login` and `api_key`:
 
 ```
 Conjur::API.new_from_key login, api_key
 ```
 
-Note that if you are connecting as a [Host](http://developer.conjur.net/reference/services/directory/host), the login should be
+Note that if you are connecting as a Host, the login should be
 prefixed with `host/`. For example: `host/myhost.example.com`, not just `myhost.example.com`.
 
 ## Configuring RestClient
 
 [Conjur::Configuration](https://github.com/conjurinc/api-ruby/blob/master/lib/conjur/configuration.rb)
 allows optional configuration of the [RestClient](https://github.com/rest-client/rest-client)
-instance used by Conjur API to communicate with the Conjur server, via the options hash
+instance used by Secrets Manager API to communicate with the Secrets Manager server, via the options hash
 `Conjur.configuration.rest_client_options`.
 
 The default value for the options hash is:

data/Rakefile

@@ -24,7 +24,7 @@ begin
   require 'cucumber/rake/task'
 
   Cucumber::Rake::Task.new(:cucumber) do |t|
-    t.cucumber_opts = "--tags ~@wip --format pretty --format junit --out features/reports"
+    t.cucumber_opts = "--tags 'not @wip' --format pretty --format junit --out features/reports"
   end
 
   begin

data/SECURITY.md

@@ -1,42 +1,6 @@
 # Security Policies and Procedures
 
-This document outlines security procedures and general policies for the CyberArk Conjur
-suite of tools and products.
-
-  * [Reporting a Bug](#reporting-a-bug)
-  * [Disclosure Policy](#disclosure-policy)
-  * [Comments on this Policy](#comments-on-this-policy)
-
 ## Reporting a Bug
+CyberArk takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you follow responsible disclosure guidelines and contact product_security@cyberark.com and work with us toward a quick resolution to protect our customers.
 
-The CyberArk Conjur team and community take all security bugs in the Conjur suite seriously.
-Thank you for improving the security of the Conjur suite. We appreciate your efforts and
-responsible disclosure and will make every effort to acknowledge your
-contributions.
-
-Report security bugs by emailing the lead maintainers at security@conjur.org.
-
-The maintainers will acknowledge your email within 2 business days. Subsequently, we will 
-send a more detailed response within 2 business days of our acknowledgement indicating
-the next steps in handling your report. After the initial reply to your report, the security
-team will endeavor to keep you informed of the progress towards a fix and full
-announcement, and may ask for additional information or guidance.
-
-Report security bugs in third-party modules to the person or team maintaining
-the module.
-
-## Disclosure Policy
-
-When the security team receives a security bug report, they will assign it to a
-primary handler. This person will coordinate the fix and release process,
-involving the following steps:
-
-  * Confirm the problem and determine the affected versions.
-  * Audit code to find any potential similar problems.
-  * Prepare fixes for all releases still under maintenance. These fixes will be
-    released as fast as possible.
-
-## Comments on this Policy
-
-If you have suggestions on how this process could be improved please submit a
-pull request.
+Refer to [CyberArk's Security Vulnerability Policy](https://www.cyberark.com/cyberark-security-vulinerability-policy.pdf) for more details.

data/VERSION

@@ -1 +1 @@
-6.0.1-523
+6.0.1-562

data/conjur-api.gemspec

@@ -29,9 +29,9 @@ Gem::Specification.new do |gem|
   gem.add_development_dependency 'rspec', '~> 3'
   gem.add_development_dependency 'rspec-expectations', '~> 3.4'
   gem.add_development_dependency 'json_spec'
-  gem.add_development_dependency 'cucumber', '~> 2.99'
+  gem.add_development_dependency 'cucumber'
   gem.add_development_dependency 'ci_reporter_rspec'
-  gem.add_development_dependency 'simplecov', '~> 0.17', '< 0.18'
+  gem.add_development_dependency 'simplecov'
   gem.add_development_dependency 'simplecov-cobertura'
   gem.add_development_dependency 'io-grab'
   gem.add_development_dependency 'rdoc'

data/features/support/env.rb

@@ -20,4 +20,4 @@ $username = ENV['CONJUR_AUTHN_LOGIN'] || 'admin'
 $password = ENV['CONJUR_AUTHN_API_KEY'] || 'secret'
 
 $api_key = Conjur::API.login $username, $password
-$conjur = Conjur::API.new_from_key $username, $api_key
+$conjur = Conjur::API.new_from_key $username, $api_key

data/spec/spec_helper.rb

@@ -114,4 +114,4 @@ shared_context logging: :temp do
   let(:logfile) { Tempfile.new("log") }
   before { Conjur.log = logfile.path }
   let(:log) { logfile.read }
-end
+end

data/test.sh

@@ -63,4 +63,4 @@ function runTests() {
     "/scripts/fetch_certificate && bundle exec rake jenkins_init jenkins_spec jenkins_cucumber"
 }
 
-main
+main

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: conjur-api
 version: !ruby/object:Gem::Version
-  version: 6.0.1.pre.523
+  version: 6.0.1.pre.562
 platform: ruby
 authors:
 - CyberArk Maintainers
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2025-08-25 00:00:00.000000000 Z
+date: 2025-10-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: rest-client
@@ -112,16 +112,16 @@ dependencies:
   name: cucumber
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '2.99'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '2.99'
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: ci_reporter_rspec
   requirement: !ruby/object:Gem::Requirement
@@ -140,22 +140,16 @@ dependencies:
   name: simplecov
   requirement: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.17'
-    - - "<"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0.18'
+        version: '0'
   type: :development
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: '0.17'
-    - - "<"
+    - - ">="
       - !ruby/object:Gem::Version
-        version: '0.18'
+        version: '0'
 - !ruby/object:Gem::Dependency
   name: simplecov-cobertura
   requirement: !ruby/object:Gem::Requirement