zyphr 0.1.47 → 0.1.48

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 1631c8b08187f685f9ba0705937529c10b793216403e569e084b19bbe76eed98
-  data.tar.gz: d459bb04c1089992c9c18a2287a5cdf859fdef80e94fe8859a78b659c4b56c4c
+  metadata.gz: 2b5e4efe27496d1705a00bd68c41d08cd989868b1c6adcfd121020427d564cd3
+  data.tar.gz: 1609dd6b8ef90f34d467818f1a118c9e098b08f1eef3f9214998ca3b954fec5f
 SHA512:
-  metadata.gz: dbdbfe7cb026b80ff24bfb3760983f9be06c4aaa2da6bdcd3d1386e29ac838c0ce1a927cfedfa48079ca3aab11dd4c6a4f47e065064c82a382253fdeeb01a14f
-  data.tar.gz: befc207eb3218353d296f8b14466fdb9fcf53a008c576381c843c998c8875bad60131e5bdb0b97785eb7bbd9aedc501e09f882ed1d3157f46f6350e771e65a1c
+  metadata.gz: b7aa153c3b521e7655329023a0e94435384ebbeff2d50bcf1a45d21b19445b4e41e20219059f5317e522b9b7804053cddadad1ec1b7def398abb16e38e6d4482
+  data.tar.gz: 3775721a2b16919ebc96ea0e792eeadb40eb14c24b8380f6e8ada9eb3a2d0c29472bb4df0a109ea369e3a7189e03424438cb7ddb035b283993059ae1f485faa6

data/docs/AuthSessionsApi.md

@@ -87,7 +87,7 @@ This endpoint does not need any parameter.
 
 Refresh access token
 
-Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
 
 ### Examples
 

data/lib/zyphr/api/auth_sessions_api.rb

@@ -77,7 +77,7 @@ module Zyphr
     end
 
     # Refresh access token
-    # Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+    # Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
     # @param refresh_session_request [RefreshSessionRequest] 
     # @param [Hash] opts the optional parameters
     # @return [RefreshTokenResponse]
@@ -87,7 +87,7 @@ module Zyphr
     end
 
     # Refresh access token
-    # Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+    # Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
     # @param refresh_session_request [RefreshSessionRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(RefreshTokenResponse, Integer, Hash)>] RefreshTokenResponse data, response status code and response headers

data/spec/api/auth_sessions_api_spec.rb

@@ -45,7 +45,7 @@ describe 'AuthSessionsApi' do
 
   # unit tests for refresh_end_user_token
   # Refresh access token
-  # Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+  # Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
   # @param refresh_session_request 
   # @param [Hash] opts the optional parameters
   # @return [RefreshTokenResponse]

data/zyphr.gemspec

@@ -17,7 +17,7 @@ require "zyphr/version"
 
 Gem::Specification.new do |s|
   s.name        = "zyphr"
-  s.version = '0.1.47'
+  s.version = '0.1.48'
   s.platform    = Gem::Platform::RUBY
   s.authors     = ["Zyphr"]
   s.email       = ["support@zyphr.dev"]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: zyphr
 version: !ruby/object:Gem::Version
-  version: 0.1.47
+  version: 0.1.48
 platform: ruby
 authors:
 - Zyphr