From 4126f92dff0ba3c9e7cea38d363fdd767da6d69d Mon Sep 17 00:00:00 2001 From: Warren Parad Date: Sun, 20 Dec 2020 18:51:11 +0100 Subject: [PATCH] Release 1.0 version --- .github/workflows/build.yml | 5 +- .gitignore | 2 - README.md | 68 +++--- docs/AccessRecord.md | 2 +- docs/AccessRecordCollection.md | 2 +- docs/AccessRecordCollectionRecords.md | 2 +- docs/AccessRecordsApi.md | 82 +++---- docs/Account.md | 2 +- docs/AccountCollection.md | 2 +- docs/AccountCollectionAccounts.md | 2 +- docs/AccountsApi.md | 36 +-- docs/Body.md | 2 +- docs/Body1.md | 2 +- docs/Body10.md | 2 +- docs/Body11.md | 2 +- docs/Body2.md | 2 +- docs/Body3.md | 2 +- docs/Body4.md | 2 +- docs/Body5.md | 2 +- docs/Body6.md | 2 +- docs/Body7.md | 2 +- docs/Body8.md | 2 +- docs/Body9.md | 2 +- docs/ClaimRequest.md | 2 +- docs/ClaimResponse.md | 2 +- docs/Client.md | 2 +- docs/ClientAccessKey.md | 2 +- docs/ClientCollection.md | 2 +- docs/ClientCollectionClients.md | 2 +- docs/Identity.md | 2 +- docs/IdentityCollection.md | 2 +- docs/IdentityCollectionIdentities.md | 2 +- docs/IdentityRequest.md | 2 +- docs/InlineResponse200.md | 2 +- docs/InlineResponse2001.md | 2 +- docs/InlineResponse20010.md | 2 +- docs/InlineResponse20011.md | 2 +- docs/InlineResponse20012.md | 2 +- docs/InlineResponse20013.md | 2 +- docs/InlineResponse20014.md | 2 +- docs/InlineResponse20015.md | 2 +- docs/InlineResponse2002.md | 2 +- docs/InlineResponse2003.md | 2 +- docs/InlineResponse2004.md | 2 +- docs/InlineResponse2005.md | 2 +- docs/InlineResponse2006.md | 2 +- docs/InlineResponse2007.md | 2 +- docs/InlineResponse2008.md | 2 +- docs/InlineResponse2009.md | 2 +- docs/Invite.md | 2 +- docs/Link.md | 2 +- docs/MetadataApi.md | 20 +- docs/MetadataObject.md | 2 +- docs/PermissionObject.md | 2 +- docs/PermissionResponse.md | 2 +- docs/ResourcePermission.md | 2 +- docs/ResourcePermissionCollection.md | 2 +- docs/ResourcePermissionCollectionLinks.md | 2 +- docs/ResourcePermissionCollectionLinksNext.md | 2 +- docs/ResourcePermissionCollectionResources.md | 2 +- docs/ResourcePermissionsApi.md | 36 +-- docs/ResourceUsersCollection.md | 2 +- docs/Role.md | 2 +- docs/RolesApi.md | 38 ++-- docs/ServiceClientsApi.md | 62 +++--- docs/Statement.md | 2 +- docs/TokenRequest.md | 2 +- docs/User.md | 2 +- docs/UserPermissionsApi.md | 44 ++-- docs/UserResources.md | 2 +- docs/UserResourcesResources.md | 2 +- docs/UserToken.md | 2 +- docs/UserTokenLinks.md | 2 +- docs/UserTokenLinksSelf.md | 2 +- docs/V1clientsOptions.md | 2 +- docs/V1recordsAccount.md | 2 +- docs/V1recordsLinks.md | 2 +- docs/V1recordsLinksSelf.md | 2 +- docs/V1recordsUsers.md | 2 +- docs/V1resourcesresourceUriPermissions.md | 2 +- docs/V1rolesPermissions.md | 2 +- ...erIdresourcesresourceUrimetadataAccount.md | 2 +- docs/V1usersuserIdtokensResources.md | 2 +- docs/V1usersuserIdtokensStatements.md | 2 +- lib/authress_sdk.rb | 18 ++ .../api/access_records_api.rb | 153 +++++++------ .../api/accounts_api.rb | 69 +++--- .../api/metadata_api.rb | 53 ++--- .../api/resource_permissions_api.rb | 73 +++---- .../api/roles_api.rb | 79 +++---- .../api/service_clients_api.rb | 119 +++++----- .../api/user_permissions_api.rb | 95 ++++---- lib/authress_sdk/api_error.rb | 50 +++++ .../authress_client.rb} | 146 +++---------- lib/authress_sdk/constant_token_provider.rb | 19 ++ .../models/access_record.rb | 15 +- .../models/access_record_collection.rb | 15 +- .../access_record_collection_records.rb | 15 +- .../models/account.rb | 15 +- .../models/account_collection.rb} | 17 +- .../models/account_collection_accounts.rb | 15 +- .../models/body.rb | 15 +- .../models/body_1.rb | 15 +- .../models/body_10.rb | 15 +- .../models/body_11.rb | 15 +- .../models/body_2.rb | 15 +- .../models/body_3.rb | 15 +- .../models/body_4.rb | 15 +- .../models/body_5.rb | 15 +- .../models/body_6.rb | 15 +- .../models/body_7.rb | 15 +- .../models/body_8.rb | 15 +- .../models/body_9.rb | 15 +- .../models/claim_request.rb | 15 +- .../models/claim_response.rb | 15 +- .../models/client.rb | 15 +- .../models/client_access_key.rb | 15 +- .../models/client_collection.rb | 15 +- .../models/client_collection_clients.rb | 15 +- .../models/identity.rb | 15 +- .../models/identity_collection.rb | 15 +- .../models/identity_collection_identities.rb | 15 +- .../models/identity_request.rb | 15 +- .../models/inline_response_200.rb | 15 +- .../models/inline_response_200_1.rb | 15 +- .../models/inline_response_200_10.rb | 15 +- .../models/inline_response_200_11.rb} | 17 +- .../models/inline_response_200_12.rb | 15 +- .../models/inline_response_200_13.rb | 15 +- .../models/inline_response_200_14.rb | 15 +- .../models/inline_response_200_15.rb | 15 +- .../models/inline_response_200_2.rb | 15 +- .../models/inline_response_200_3.rb | 15 +- .../models/inline_response_200_4.rb | 15 +- .../models/inline_response_200_5.rb | 15 +- .../models/inline_response_200_6.rb | 15 +- .../models/inline_response_200_7.rb | 15 +- .../models/inline_response_200_8.rb | 15 +- .../models/inline_response_200_9.rb | 15 +- .../models/invite.rb | 15 +- .../models/link.rb | 15 +- .../models/metadata_object.rb | 15 +- .../models/permission_object.rb} | 17 +- .../models/permission_response.rb | 15 +- .../models/resource_permission.rb | 15 +- .../models/resource_permission_collection.rb | 15 +- .../resource_permission_collection_links.rb | 15 +- ...source_permission_collection_links_next.rb | 15 +- ...esource_permission_collection_resources.rb | 15 +- .../models/resource_users_collection.rb | 15 +- .../models/role.rb | 15 +- .../models/statement.rb | 15 +- .../models/token_request.rb | 15 +- .../models/user.rb | 15 +- .../models/user_resources.rb | 15 +- .../models/user_resources_resources.rb | 15 +- .../models/user_token.rb | 15 +- .../models/user_token_links.rb | 15 +- .../models/user_token_links_self.rb | 15 +- .../models/v1clients_options.rb | 15 +- .../models/v1records_account.rb | 15 +- .../models/v1records_links.rb | 15 +- .../models/v1records_links_self.rb | 15 +- .../models/v1records_users.rb | 15 +- .../v1resourcesresource_uri_permissions.rb | 15 +- .../models/v1roles_permissions.rb} | 17 +- ...idresourcesresource_urimetadata_account.rb | 15 +- .../models/v1usersuser_idtokens_resources.rb | 15 +- .../models/v1usersuser_idtokens_statements.rb | 15 +- .../service_client_token_provider.rb | 18 ++ lib/swagger_client.rb | 30 --- lib/swagger_client/api_error.rb | 57 ----- lib/swagger_client/configuration.rb | 205 ------------------ lib/swagger_client/version.rb | 14 -- spec/api/access_records_api_spec.rb | 15 +- spec/api/accounts_api_spec.rb | 15 +- spec/api/metadata_api_spec.rb | 15 +- spec/api/resource_permissions_api_spec.rb | 15 +- spec/api/roles_api_spec.rb | 15 +- spec/api/service_clients_api_spec.rb | 15 +- spec/api/user_permissions_api_spec.rb | 15 +- spec/api_client_spec.rb | 189 +++++----------- spec/configuration_spec.rb | 41 ---- spec/constant_token_provider_spec.rb | 16 ++ .../access_record_collection_records_spec.rb | 15 +- spec/models/access_record_collection_spec.rb | 15 +- spec/models/access_record_spec.rb | 15 +- .../account_collection_accounts_spec.rb | 15 +- spec/models/account_collection_spec.rb | 15 +- spec/models/account_spec.rb | 15 +- spec/models/body_10_spec.rb | 15 +- spec/models/body_11_spec.rb | 15 +- spec/models/body_1_spec.rb | 15 +- spec/models/body_2_spec.rb | 15 +- spec/models/body_3_spec.rb | 15 +- spec/models/body_4_spec.rb | 15 +- spec/models/body_5_spec.rb | 15 +- spec/models/body_6_spec.rb | 15 +- spec/models/body_7_spec.rb | 15 +- spec/models/body_8_spec.rb | 15 +- spec/models/body_9_spec.rb | 15 +- spec/models/body_spec.rb | 15 +- spec/models/claim_request_spec.rb | 15 +- spec/models/claim_response_spec.rb | 15 +- spec/models/client_access_key_spec.rb | 15 +- spec/models/client_collection_clients_spec.rb | 15 +- spec/models/client_collection_spec.rb | 15 +- spec/models/client_spec.rb | 15 +- .../identity_collection_identities_spec.rb | 15 +- spec/models/identity_collection_spec.rb | 15 +- spec/models/identity_request_spec.rb | 15 +- spec/models/identity_spec.rb | 15 +- spec/models/inline_response_200_10_spec.rb | 15 +- spec/models/inline_response_200_11_spec.rb | 15 +- spec/models/inline_response_200_12_spec.rb | 15 +- spec/models/inline_response_200_13_spec.rb | 15 +- spec/models/inline_response_200_14_spec.rb | 15 +- spec/models/inline_response_200_15_spec.rb | 15 +- spec/models/inline_response_200_1_spec.rb | 15 +- spec/models/inline_response_200_2_spec.rb | 15 +- spec/models/inline_response_200_3_spec.rb | 15 +- spec/models/inline_response_200_4_spec.rb | 15 +- spec/models/inline_response_200_5_spec.rb | 15 +- spec/models/inline_response_200_6_spec.rb | 15 +- spec/models/inline_response_200_7_spec.rb | 15 +- spec/models/inline_response_200_8_spec.rb | 15 +- spec/models/inline_response_200_9_spec.rb | 15 +- spec/models/inline_response_200_spec.rb | 15 +- spec/models/invite_spec.rb | 15 +- spec/models/link_spec.rb | 15 +- spec/models/metadata_object_spec.rb | 15 +- spec/models/permission_object_spec.rb | 15 +- spec/models/permission_response_spec.rb | 15 +- ...e_permission_collection_links_next_spec.rb | 15 +- ...source_permission_collection_links_spec.rb | 15 +- ...ce_permission_collection_resources_spec.rb | 15 +- .../resource_permission_collection_spec.rb | 15 +- spec/models/resource_permission_spec.rb | 15 +- spec/models/resource_users_collection_spec.rb | 15 +- spec/models/role_spec.rb | 15 +- spec/models/statement_spec.rb | 15 +- spec/models/token_request_spec.rb | 15 +- spec/models/user_resources_resources_spec.rb | 15 +- spec/models/user_resources_spec.rb | 15 +- spec/models/user_spec.rb | 15 +- spec/models/user_token_links_self_spec.rb | 15 +- spec/models/user_token_links_spec.rb | 15 +- spec/models/user_token_spec.rb | 15 +- spec/models/v1clients_options_spec.rb | 15 +- spec/models/v1records_account_spec.rb | 15 +- spec/models/v1records_links_self_spec.rb | 15 +- spec/models/v1records_links_spec.rb | 15 +- spec/models/v1records_users_spec.rb | 15 +- ...1resourcesresource_uri_permissions_spec.rb | 15 +- spec/models/v1roles_permissions_spec.rb | 15 +- ...ourcesresource_urimetadata_account_spec.rb | 15 +- .../v1usersuser_idtokens_resources_spec.rb | 15 +- .../v1usersuser_idtokens_statements_spec.rb | 15 +- spec/service_client_token_provider_spec.rb | 16 ++ spec/spec_helper.rb | 9 +- 260 files changed, 1419 insertions(+), 2924 deletions(-) create mode 100644 lib/authress_sdk.rb rename lib/{swagger_client => authress_sdk}/api/access_records_api.rb (72%) rename lib/{swagger_client => authress_sdk}/api/accounts_api.rb (61%) rename lib/{swagger_client => authress_sdk}/api/metadata_api.rb (67%) rename lib/{swagger_client => authress_sdk}/api/resource_permissions_api.rb (68%) rename lib/{swagger_client => authress_sdk}/api/roles_api.rb (61%) rename lib/{swagger_client => authress_sdk}/api/service_clients_api.rb (69%) rename lib/{swagger_client => authress_sdk}/api/user_permissions_api.rb (75%) create mode 100644 lib/authress_sdk/api_error.rb rename lib/{swagger_client/api_client.rb => authress_sdk/authress_client.rb} (57%) create mode 100644 lib/authress_sdk/constant_token_provider.rb rename lib/{swagger_client => authress_sdk}/models/access_record.rb (79%) rename lib/{swagger_client => authress_sdk}/models/access_record_collection.rb (70%) rename lib/{swagger_client => authress_sdk}/models/access_record_collection_records.rb (79%) rename lib/{swagger_client => authress_sdk}/models/account.rb (74%) rename lib/{swagger_client/models/inline_response_200_11.rb => authress_sdk/models/account_collection.rb} (69%) rename lib/{swagger_client => authress_sdk}/models/account_collection_accounts.rb (74%) rename lib/{swagger_client => authress_sdk}/models/body.rb (72%) rename lib/{swagger_client => authress_sdk}/models/body_1.rb (71%) rename lib/{swagger_client => authress_sdk}/models/body_10.rb (72%) rename lib/{swagger_client => authress_sdk}/models/body_11.rb (72%) rename lib/{swagger_client => authress_sdk}/models/body_2.rb (69%) rename lib/{swagger_client => authress_sdk}/models/body_3.rb (79%) rename lib/{swagger_client => authress_sdk}/models/body_4.rb (79%) rename lib/{swagger_client => authress_sdk}/models/body_5.rb (71%) rename lib/{swagger_client => authress_sdk}/models/body_6.rb (73%) rename lib/{swagger_client => authress_sdk}/models/body_7.rb (73%) rename lib/{swagger_client => authress_sdk}/models/body_8.rb (72%) rename lib/{swagger_client => authress_sdk}/models/body_9.rb (71%) rename lib/{swagger_client => authress_sdk}/models/claim_request.rb (72%) rename lib/{swagger_client => authress_sdk}/models/claim_response.rb (67%) rename lib/{swagger_client => authress_sdk}/models/client.rb (72%) rename lib/{swagger_client => authress_sdk}/models/client_access_key.rb (73%) rename lib/{swagger_client => authress_sdk}/models/client_collection.rb (70%) rename lib/{swagger_client => authress_sdk}/models/client_collection_clients.rb (72%) rename lib/{swagger_client => authress_sdk}/models/identity.rb (71%) rename lib/{swagger_client => authress_sdk}/models/identity_collection.rb (69%) rename lib/{swagger_client => authress_sdk}/models/identity_collection_identities.rb (71%) rename lib/{swagger_client => authress_sdk}/models/identity_request.rb (71%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200.rb (72%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_1.rb (72%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_10.rb (73%) rename lib/{swagger_client/models/account_collection.rb => authress_sdk/models/inline_response_200_11.rb} (70%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_12.rb (69%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_13.rb (70%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_14.rb (72%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_15.rb (73%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_2.rb (72%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_3.rb (73%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_4.rb (71%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_5.rb (69%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_6.rb (70%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_7.rb (70%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_8.rb (79%) rename lib/{swagger_client => authress_sdk}/models/inline_response_200_9.rb (74%) rename lib/{swagger_client => authress_sdk}/models/invite.rb (71%) rename lib/{swagger_client => authress_sdk}/models/link.rb (71%) rename lib/{swagger_client => authress_sdk}/models/metadata_object.rb (72%) rename lib/{swagger_client/models/v1roles_permissions.rb => authress_sdk/models/permission_object.rb} (74%) rename lib/{swagger_client => authress_sdk}/models/permission_response.rb (72%) rename lib/{swagger_client => authress_sdk}/models/resource_permission.rb (69%) rename lib/{swagger_client => authress_sdk}/models/resource_permission_collection.rb (70%) rename lib/{swagger_client => authress_sdk}/models/resource_permission_collection_links.rb (69%) rename lib/{swagger_client => authress_sdk}/models/resource_permission_collection_links_next.rb (70%) rename lib/{swagger_client => authress_sdk}/models/resource_permission_collection_resources.rb (69%) rename lib/{swagger_client => authress_sdk}/models/resource_users_collection.rb (70%) rename lib/{swagger_client => authress_sdk}/models/role.rb (73%) rename lib/{swagger_client => authress_sdk}/models/statement.rb (71%) rename lib/{swagger_client => authress_sdk}/models/token_request.rb (71%) rename lib/{swagger_client => authress_sdk}/models/user.rb (69%) rename lib/{swagger_client => authress_sdk}/models/user_resources.rb (72%) rename lib/{swagger_client => authress_sdk}/models/user_resources_resources.rb (69%) rename lib/{swagger_client => authress_sdk}/models/user_token.rb (73%) rename lib/{swagger_client => authress_sdk}/models/user_token_links.rb (69%) rename lib/{swagger_client => authress_sdk}/models/user_token_links_self.rb (70%) rename lib/{swagger_client => authress_sdk}/models/v1clients_options.rb (71%) rename lib/{swagger_client => authress_sdk}/models/v1records_account.rb (69%) rename lib/{swagger_client => authress_sdk}/models/v1records_links.rb (69%) rename lib/{swagger_client => authress_sdk}/models/v1records_links_self.rb (70%) rename lib/{swagger_client => authress_sdk}/models/v1records_users.rb (69%) rename lib/{swagger_client => authress_sdk}/models/v1resourcesresource_uri_permissions.rb (73%) rename lib/{swagger_client/models/permission_object.rb => authress_sdk/models/v1roles_permissions.rb} (75%) rename lib/{swagger_client => authress_sdk}/models/v1usersuser_idresourcesresource_urimetadata_account.rb (68%) rename lib/{swagger_client => authress_sdk}/models/v1usersuser_idtokens_resources.rb (69%) rename lib/{swagger_client => authress_sdk}/models/v1usersuser_idtokens_statements.rb (70%) create mode 100644 lib/authress_sdk/service_client_token_provider.rb delete mode 100644 lib/swagger_client.rb delete mode 100644 lib/swagger_client/api_error.rb delete mode 100644 lib/swagger_client/configuration.rb delete mode 100644 lib/swagger_client/version.rb delete mode 100644 spec/configuration_spec.rb create mode 100644 spec/constant_token_provider_spec.rb create mode 100644 spec/service_client_token_provider_spec.rb diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index efcce9d..fd7050f 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -24,12 +24,13 @@ jobs: run: gem install bundler:'~> 2.2.2' && bundle install - name: Run build - run: bundle exec rake --trace + run: | + bundle exec rake --trace + bundle exec rake build --trace - name: Deploy to RubyGems if: github.ref != 'refs/heads/main' && github.event_name == 'push' run: | - bundle exec rake build --trace bundle exec rake publish_git_tag --trace gem push pkg/*.gem -V env: diff --git a/.gitignore b/.gitignore index c021594..d696af2 100644 --- a/.gitignore +++ b/.gitignore @@ -1,5 +1,3 @@ -# Generated by: https://github.com/swagger-api/swagger-codegen.git -# *.gem *.rbc diff --git a/README.md b/README.md index 37a0477..d58a98a 100644 --- a/README.md +++ b/README.md @@ -12,86 +12,86 @@ gem install authress-sdk Then required the package: ```rb -require 'authress-sdk'; +require 'authress-sdk' ``` ## Getting started examples ### Authorize using a user token ```rb -require 'authress-sdk'; +require 'authress-sdk' # create an instance of the API class during service initialization # Replace DOMAIN with the Authress domain for your account -AuthressClient.configure do |config| +AuthressSdk.configure do |config| config.base_url = 'https://DOMAIN.api-REGION.authress.io' end # on api route [route('/resources/')] -function getResource(resourceId) { +def getResource(resourceId) # Get the user token and pass it to authress - authorizationToken = request.headers.get('authorization'); - AuthressClient.setToken(authorizationToken); + authorizationToken = request.headers.get('authorization') + AuthressSdk::AuthressClient.set_token(authorizationToken) # Check Authress to authorize the user user_id = 'user_id_example' # String | The user to check permissions on - resource_uri = `resources/${resourceId}` # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed, the resource must be a full path, and permissions are not inherited by sub-resources. + resource_uri = "resources/#{resourceId}" # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed, the resource must be a full path, and permissions are not inherited by sub-resources. permission = 'READ' # String | Permission to check, '*' and scoped permissions can also be checked here. begin #Check to see if a user has permissions to a resource. - api_instance = SwaggerClient::UserPermissionsApi.new + api_instance = AuthressSdk::UserPermissionsApi.new api_instance.authorize_user(user_id, resource_uri, permission) - rescue SwaggerClient::ApiError => e + rescue AuthressSdk::ApiError => e # Will throw except if the user is not authorized to read the resource if (e.status === 404) { - return { statusCode: 404 }; + return { statusCode: 404 } } puts "Exception when calling UserPermissionsApi->authorize_user: #{e}" - throw e; + raise end # On success, continue with the route code to load resource and return it - return { resource: {}, statusCode: 200 }; + return { resource: {}, statusCode: 200 } ``` ### Authorize with a service client ```rb -require 'authress-sdk'; +require 'authress-sdk' # create an instance of the API class during service initialization # Replace DOMAIN with the Authress domain for your account # Create a service client in the Authress management portal and past the access token here # This will generate a token automatically instead of passing the user token to the api -AuthressClient.configure do |config| +AuthressSdk.configure do |config| config.base_url = 'https://DOMAIN.api-REGION.authress.io' - accessToken = 'eyJrZXlJ....'; - config.token_provider = ServiceClientTokenProvider.new(accessToken) + client_access_key = 'eyJrZXlJ....' + config.token_provider = AuthressSdk::ServiceClientTokenProvider.new(client_access_key) end # on api route [route('/resources/')] -function getResource(resourceId) { +def getResource(resourceId) { # Check Authress to authorize the user user_id = 'user_id_example' # String | The user to check permissions on - resource_uri = `resources/${resourceId}` # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed, the resource must be a full path, and permissions are not inherited by sub-resources. + resource_uri = "resources/#{resourceId}" # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed, the resource must be a full path, and permissions are not inherited by sub-resources. permission = 'READ' # String | Permission to check, '*' and scoped permissions can also be checked here. begin #Check to see if a user has permissions to a resource. - api_instance = SwaggerClient::UserPermissionsApi.new + api_instance = AuthressSdk::UserPermissionsApi.new api_instance.authorize_user(user_id, resource_uri, permission) - rescue SwaggerClient::ApiError => e - # Will throw except if the user is not authorized to read the resource + rescue AuthressSdk::ApiError => e + # Will raise exception if the user is not authorized to read the resource if (e.status === 404) { - return { statusCode: 404 }; + return { statusCode: 404 } } puts "Exception when calling UserPermissionsApi->authorize_user: #{e}" - throw e; + raise end # On success, continue with the route code to load resource and return it - return { resource: {}, statusCode: 200 }; + return { resource: {}, statusCode: 200 } ``` ### Creating resources @@ -100,23 +100,27 @@ When a user creates a resource in your application, we want to ensure that they You may receive **User does not have sufficient access to grant permissions to resources** as an error along with the status code **403**. This means that the service client or user jwt does not have access to create the access record. If using a service client, go to the Authress portal and create a one time record which grants the service client `Authress:Owner` to `Resources/` so that it can manage access records for these types of resources. ```rb -require 'authress-sdk'; +require 'authress-sdk' begin #Create a new access record. - new_record = SwaggerClient::Body3.new { - name: `Access To New Resource ${NewResourceId}`, + new_record = AuthressSdk::Body3.new { + name: "Access To New Resource #{NewResourceId}", users: [{ userId: requestUserId }], statements: [{ - resources: [{ resourceUri: `Resources/${NewResourceId}` }], + resources: [{ resourceUri: "Resources/#{NewResourceId}" }], # Owner by default gives full control over this new resource, including the ability to grant others access as well. roles: ['Authress:Owner'] }] - }; - api_instance = SwaggerClient::AccessRecordsApi.new + } + api_instance = AuthressSdk::AccessRecordsApi.new result = api_instance.create_record(new_record) puts result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->create_record: #{e}" + raise end -``` \ No newline at end of file +``` + +### Early release +* Add in access_token handling to client \ No newline at end of file diff --git a/docs/AccessRecord.md b/docs/AccessRecord.md index 8c6b569..96140e1 100644 --- a/docs/AccessRecord.md +++ b/docs/AccessRecord.md @@ -1,4 +1,4 @@ -# SwaggerClient::AccessRecord +# AuthressSdk::AccessRecord ## Properties Name | Type | Description | Notes diff --git a/docs/AccessRecordCollection.md b/docs/AccessRecordCollection.md index 7320279..82c8e09 100644 --- a/docs/AccessRecordCollection.md +++ b/docs/AccessRecordCollection.md @@ -1,4 +1,4 @@ -# SwaggerClient::AccessRecordCollection +# AuthressSdk::AccessRecordCollection ## Properties Name | Type | Description | Notes diff --git a/docs/AccessRecordCollectionRecords.md b/docs/AccessRecordCollectionRecords.md index c8885b9..c60eb7e 100644 --- a/docs/AccessRecordCollectionRecords.md +++ b/docs/AccessRecordCollectionRecords.md @@ -1,4 +1,4 @@ -# SwaggerClient::AccessRecordCollectionRecords +# AuthressSdk::AccessRecordCollectionRecords ## Properties Name | Type | Description | Notes diff --git a/docs/AccessRecordsApi.md b/docs/AccessRecordsApi.md index bafcbe8..eb0256a 100644 --- a/docs/AccessRecordsApi.md +++ b/docs/AccessRecordsApi.md @@ -1,4 +1,4 @@ -# SwaggerClient::AccessRecordsApi +# AuthressSdk::AccessRecordsApi All URIs are relative to */* @@ -24,20 +24,20 @@ Claim a resource by allowing a user to pick an identifier and receive admin acce ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new -body = SwaggerClient::Body8.new # Body8 | +api_instance = AuthressSdk::AccessRecordsApi.new +body = AuthressSdk::Body8.new # Body8 | begin #Claim a resource by an allowed user. result = api_instance.create_claim(body) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->create_claim: #{e}" end ``` @@ -73,19 +73,19 @@ Invites are used to easily assign permissions to users that have not been create ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new -body = SwaggerClient::Body5.new # Body5 | +api_instance = AuthressSdk::AccessRecordsApi.new +body = AuthressSdk::Body5.new # Body5 | begin #Create a new invite. api_instance.create_invite(body) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->create_invite: #{e}" end ``` @@ -121,20 +121,20 @@ Specify user roles for specific resources. (Records have a maximum size of ~100K ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new -body = SwaggerClient::Body3.new # Body3 | +api_instance = AuthressSdk::AccessRecordsApi.new +body = AuthressSdk::Body3.new # Body3 | begin #Create a new access record. result = api_instance.create_record(body) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->create_record: #{e}" end ``` @@ -170,19 +170,19 @@ Deletes an invite.
REA ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new +api_instance = AuthressSdk::AccessRecordsApi.new invite_id = 'invite_id_example' # String | The identifier of the invite. begin #Delete an invite. api_instance.delete_invite(invite_id) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->delete_invite: #{e}" end ``` @@ -218,19 +218,19 @@ Remove an access record, removing associated permissions from all users in recor ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new +api_instance = AuthressSdk::AccessRecordsApi.new record_id = 'record_id_example' # String | The identifier of the access record. begin #Deletes an access record. api_instance.delete_record(record_id) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->delete_record: #{e}" end ``` @@ -266,12 +266,12 @@ Access records contain information assigning permissions to users for resources. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new +api_instance = AuthressSdk::AccessRecordsApi.new record_id = 'record_id_example' # String | The identifier of the access record. @@ -279,7 +279,7 @@ begin #Get an access record for the account. result = api_instance.get_record(record_id) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->get_record: #{e}" end ``` @@ -315,12 +315,12 @@ Get all account records. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new +api_instance = AuthressSdk::AccessRecordsApi.new opts = { limit: 20, # Integer | Max number of results to return cursor: 'cursor_example', # String | Continuation cursor for paging (will automatically be set) @@ -332,7 +332,7 @@ begin #Get all account records. result = api_instance.get_records(opts) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->get_records: #{e}" end ``` @@ -371,12 +371,12 @@ Accepts an invite by claiming this invite by this user. The user token used for ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new +api_instance = AuthressSdk::AccessRecordsApi.new invite_id = 'invite_id_example' # String | The identifier of the invite. @@ -384,7 +384,7 @@ begin #Accept an invite. result = api_instance.respond_to_invite(invite_id) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->respond_to_invite: #{e}" end ``` @@ -420,13 +420,13 @@ Updates an access record adding or removing user permissions to resources. (Reco ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccessRecordsApi.new -body = SwaggerClient::Body4.new # Body4 | +api_instance = AuthressSdk::AccessRecordsApi.new +body = AuthressSdk::Body4.new # Body4 | record_id = 'record_id_example' # String | The identifier of the access record. @@ -434,7 +434,7 @@ begin #Update an access record. result = api_instance.update_record(bodyrecord_id) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccessRecordsApi->update_record: #{e}" end ``` diff --git a/docs/Account.md b/docs/Account.md index 0fe25e9..69e7a98 100644 --- a/docs/Account.md +++ b/docs/Account.md @@ -1,4 +1,4 @@ -# SwaggerClient::Account +# AuthressSdk::Account ## Properties Name | Type | Description | Notes diff --git a/docs/AccountCollection.md b/docs/AccountCollection.md index 1edac6d..6746946 100644 --- a/docs/AccountCollection.md +++ b/docs/AccountCollection.md @@ -1,4 +1,4 @@ -# SwaggerClient::AccountCollection +# AuthressSdk::AccountCollection ## Properties Name | Type | Description | Notes diff --git a/docs/AccountCollectionAccounts.md b/docs/AccountCollectionAccounts.md index c128e15..a7507b8 100644 --- a/docs/AccountCollectionAccounts.md +++ b/docs/AccountCollectionAccounts.md @@ -1,4 +1,4 @@ -# SwaggerClient::AccountCollectionAccounts +# AuthressSdk::AccountCollectionAccounts ## Properties Name | Type | Description | Notes diff --git a/docs/AccountsApi.md b/docs/AccountsApi.md index 65e7127..7ccfddc 100644 --- a/docs/AccountsApi.md +++ b/docs/AccountsApi.md @@ -1,4 +1,4 @@ -# SwaggerClient::AccountsApi +# AuthressSdk::AccountsApi All URIs are relative to */* @@ -19,12 +19,12 @@ Includes the original configuration information.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccountsApi->get_account: #{e}" end ``` @@ -68,18 +68,18 @@ Returns a list of identities linked for this account.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccountsApi->get_account_identities: #{e}" end ``` @@ -112,18 +112,18 @@ Returns a list of accounts that the user has access to.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccountsApi->get_accounts: #{e}" end ``` @@ -156,19 +156,19 @@ An identity is a JWT subscriber *sub* and issuer *iss*. Only one account my be l ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::AccountsApi.new -body = SwaggerClient::Body9.new # Body9 | +api_instance = AuthressSdk::AccountsApi.new +body = AuthressSdk::Body9.new # Body9 | begin #Link a new account identity. api_instance.link_identity(body) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling AccountsApi->link_identity: #{e}" end ``` diff --git a/docs/Body.md b/docs/Body.md index c854c0a..dfe7a05 100644 --- a/docs/Body.md +++ b/docs/Body.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body +# AuthressSdk::Body ## Properties Name | Type | Description | Notes diff --git a/docs/Body1.md b/docs/Body1.md index 41c58cc..9fe68b5 100644 --- a/docs/Body1.md +++ b/docs/Body1.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body1 +# AuthressSdk::Body1 ## Properties Name | Type | Description | Notes diff --git a/docs/Body10.md b/docs/Body10.md index 246690f..e56c91a 100644 --- a/docs/Body10.md +++ b/docs/Body10.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body10 +# AuthressSdk::Body10 ## Properties Name | Type | Description | Notes diff --git a/docs/Body11.md b/docs/Body11.md index c8f4b2b..c751523 100644 --- a/docs/Body11.md +++ b/docs/Body11.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body11 +# AuthressSdk::Body11 ## Properties Name | Type | Description | Notes diff --git a/docs/Body2.md b/docs/Body2.md index e5c13aa..e9ac6a3 100644 --- a/docs/Body2.md +++ b/docs/Body2.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body2 +# AuthressSdk::Body2 ## Properties Name | Type | Description | Notes diff --git a/docs/Body3.md b/docs/Body3.md index 20858aa..afaa09d 100644 --- a/docs/Body3.md +++ b/docs/Body3.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body3 +# AuthressSdk::Body3 ## Properties Name | Type | Description | Notes diff --git a/docs/Body4.md b/docs/Body4.md index f6a242e..53053bb 100644 --- a/docs/Body4.md +++ b/docs/Body4.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body4 +# AuthressSdk::Body4 ## Properties Name | Type | Description | Notes diff --git a/docs/Body5.md b/docs/Body5.md index 5f04435..13967f5 100644 --- a/docs/Body5.md +++ b/docs/Body5.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body5 +# AuthressSdk::Body5 ## Properties Name | Type | Description | Notes diff --git a/docs/Body6.md b/docs/Body6.md index 6c9c476..00b19fb 100644 --- a/docs/Body6.md +++ b/docs/Body6.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body6 +# AuthressSdk::Body6 ## Properties Name | Type | Description | Notes diff --git a/docs/Body7.md b/docs/Body7.md index 26fcc83..d96137d 100644 --- a/docs/Body7.md +++ b/docs/Body7.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body7 +# AuthressSdk::Body7 ## Properties Name | Type | Description | Notes diff --git a/docs/Body8.md b/docs/Body8.md index 0fabd58..ebe669b 100644 --- a/docs/Body8.md +++ b/docs/Body8.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body8 +# AuthressSdk::Body8 ## Properties Name | Type | Description | Notes diff --git a/docs/Body9.md b/docs/Body9.md index 4942295..c0a1025 100644 --- a/docs/Body9.md +++ b/docs/Body9.md @@ -1,4 +1,4 @@ -# SwaggerClient::Body9 +# AuthressSdk::Body9 ## Properties Name | Type | Description | Notes diff --git a/docs/ClaimRequest.md b/docs/ClaimRequest.md index 1da25c8..dc96d69 100644 --- a/docs/ClaimRequest.md +++ b/docs/ClaimRequest.md @@ -1,4 +1,4 @@ -# SwaggerClient::ClaimRequest +# AuthressSdk::ClaimRequest ## Properties Name | Type | Description | Notes diff --git a/docs/ClaimResponse.md b/docs/ClaimResponse.md index 4132adc..53d631e 100644 --- a/docs/ClaimResponse.md +++ b/docs/ClaimResponse.md @@ -1,4 +1,4 @@ -# SwaggerClient::ClaimResponse +# AuthressSdk::ClaimResponse ## Properties Name | Type | Description | Notes diff --git a/docs/Client.md b/docs/Client.md index 77fe4bc..e3aaa63 100644 --- a/docs/Client.md +++ b/docs/Client.md @@ -1,4 +1,4 @@ -# SwaggerClient::Client +# AuthressSdk::Client ## Properties Name | Type | Description | Notes diff --git a/docs/ClientAccessKey.md b/docs/ClientAccessKey.md index 981323f..e111a7f 100644 --- a/docs/ClientAccessKey.md +++ b/docs/ClientAccessKey.md @@ -1,4 +1,4 @@ -# SwaggerClient::ClientAccessKey +# AuthressSdk::ClientAccessKey ## Properties Name | Type | Description | Notes diff --git a/docs/ClientCollection.md b/docs/ClientCollection.md index 00dabc4..0885984 100644 --- a/docs/ClientCollection.md +++ b/docs/ClientCollection.md @@ -1,4 +1,4 @@ -# SwaggerClient::ClientCollection +# AuthressSdk::ClientCollection ## Properties Name | Type | Description | Notes diff --git a/docs/ClientCollectionClients.md b/docs/ClientCollectionClients.md index f258a31..22b9d57 100644 --- a/docs/ClientCollectionClients.md +++ b/docs/ClientCollectionClients.md @@ -1,4 +1,4 @@ -# SwaggerClient::ClientCollectionClients +# AuthressSdk::ClientCollectionClients ## Properties Name | Type | Description | Notes diff --git a/docs/Identity.md b/docs/Identity.md index e90aee4..f0788c2 100644 --- a/docs/Identity.md +++ b/docs/Identity.md @@ -1,4 +1,4 @@ -# SwaggerClient::Identity +# AuthressSdk::Identity ## Properties Name | Type | Description | Notes diff --git a/docs/IdentityCollection.md b/docs/IdentityCollection.md index 3b2e232..bcaba36 100644 --- a/docs/IdentityCollection.md +++ b/docs/IdentityCollection.md @@ -1,4 +1,4 @@ -# SwaggerClient::IdentityCollection +# AuthressSdk::IdentityCollection ## Properties Name | Type | Description | Notes diff --git a/docs/IdentityCollectionIdentities.md b/docs/IdentityCollectionIdentities.md index 72577d1..6f03911 100644 --- a/docs/IdentityCollectionIdentities.md +++ b/docs/IdentityCollectionIdentities.md @@ -1,4 +1,4 @@ -# SwaggerClient::IdentityCollectionIdentities +# AuthressSdk::IdentityCollectionIdentities ## Properties Name | Type | Description | Notes diff --git a/docs/IdentityRequest.md b/docs/IdentityRequest.md index 1eb210b..ad517a7 100644 --- a/docs/IdentityRequest.md +++ b/docs/IdentityRequest.md @@ -1,4 +1,4 @@ -# SwaggerClient::IdentityRequest +# AuthressSdk::IdentityRequest ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse200.md b/docs/InlineResponse200.md index f8e419b..962273e 100644 --- a/docs/InlineResponse200.md +++ b/docs/InlineResponse200.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse200 +# AuthressSdk::InlineResponse200 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2001.md b/docs/InlineResponse2001.md index 0c96635..e3eb6fd 100644 --- a/docs/InlineResponse2001.md +++ b/docs/InlineResponse2001.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2001 +# AuthressSdk::InlineResponse2001 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse20010.md b/docs/InlineResponse20010.md index eb90aee..01e0ccc 100644 --- a/docs/InlineResponse20010.md +++ b/docs/InlineResponse20010.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse20010 +# AuthressSdk::InlineResponse20010 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse20011.md b/docs/InlineResponse20011.md index 61293a6..2481f62 100644 --- a/docs/InlineResponse20011.md +++ b/docs/InlineResponse20011.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse20011 +# AuthressSdk::InlineResponse20011 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse20012.md b/docs/InlineResponse20012.md index 3769e3f..c421b66 100644 --- a/docs/InlineResponse20012.md +++ b/docs/InlineResponse20012.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse20012 +# AuthressSdk::InlineResponse20012 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse20013.md b/docs/InlineResponse20013.md index 8937db3..add8c5f 100644 --- a/docs/InlineResponse20013.md +++ b/docs/InlineResponse20013.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse20013 +# AuthressSdk::InlineResponse20013 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse20014.md b/docs/InlineResponse20014.md index f369a60..fa635d7 100644 --- a/docs/InlineResponse20014.md +++ b/docs/InlineResponse20014.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse20014 +# AuthressSdk::InlineResponse20014 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse20015.md b/docs/InlineResponse20015.md index 0de9639..ad18b12 100644 --- a/docs/InlineResponse20015.md +++ b/docs/InlineResponse20015.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse20015 +# AuthressSdk::InlineResponse20015 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2002.md b/docs/InlineResponse2002.md index f0e4377..32988f6 100644 --- a/docs/InlineResponse2002.md +++ b/docs/InlineResponse2002.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2002 +# AuthressSdk::InlineResponse2002 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2003.md b/docs/InlineResponse2003.md index 681b338..e4e033d 100644 --- a/docs/InlineResponse2003.md +++ b/docs/InlineResponse2003.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2003 +# AuthressSdk::InlineResponse2003 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2004.md b/docs/InlineResponse2004.md index 01aad2d..fee8895 100644 --- a/docs/InlineResponse2004.md +++ b/docs/InlineResponse2004.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2004 +# AuthressSdk::InlineResponse2004 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2005.md b/docs/InlineResponse2005.md index a5cbe84..5839f8d 100644 --- a/docs/InlineResponse2005.md +++ b/docs/InlineResponse2005.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2005 +# AuthressSdk::InlineResponse2005 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2006.md b/docs/InlineResponse2006.md index 4678a4b..584c53d 100644 --- a/docs/InlineResponse2006.md +++ b/docs/InlineResponse2006.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2006 +# AuthressSdk::InlineResponse2006 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2007.md b/docs/InlineResponse2007.md index e6b5baa..b93ea33 100644 --- a/docs/InlineResponse2007.md +++ b/docs/InlineResponse2007.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2007 +# AuthressSdk::InlineResponse2007 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2008.md b/docs/InlineResponse2008.md index 6e28460..ff99292 100644 --- a/docs/InlineResponse2008.md +++ b/docs/InlineResponse2008.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2008 +# AuthressSdk::InlineResponse2008 ## Properties Name | Type | Description | Notes diff --git a/docs/InlineResponse2009.md b/docs/InlineResponse2009.md index acd6c7e..002f81b 100644 --- a/docs/InlineResponse2009.md +++ b/docs/InlineResponse2009.md @@ -1,4 +1,4 @@ -# SwaggerClient::InlineResponse2009 +# AuthressSdk::InlineResponse2009 ## Properties Name | Type | Description | Notes diff --git a/docs/Invite.md b/docs/Invite.md index 9a0e3bf..99ce90f 100644 --- a/docs/Invite.md +++ b/docs/Invite.md @@ -1,4 +1,4 @@ -# SwaggerClient::Invite +# AuthressSdk::Invite ## Properties Name | Type | Description | Notes diff --git a/docs/Link.md b/docs/Link.md index 747868e..5b3e48b 100644 --- a/docs/Link.md +++ b/docs/Link.md @@ -1,4 +1,4 @@ -# SwaggerClient::Link +# AuthressSdk::Link ## Properties Name | Type | Description | Notes diff --git a/docs/MetadataApi.md b/docs/MetadataApi.md index 4f21e64..fa4db5e 100644 --- a/docs/MetadataApi.md +++ b/docs/MetadataApi.md @@ -1,4 +1,4 @@ -# SwaggerClient::MetadataApi +# AuthressSdk::MetadataApi All URIs are relative to */* @@ -17,12 +17,12 @@ Get the metadata for a resource. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::MetadataApi.new +api_instance = AuthressSdk::MetadataApi.new user_id = 'user_id_example' # String | The owner of the data. resource_uri = 'resource_uri_example' # String | The resource the data is attached to. @@ -31,7 +31,7 @@ begin #Get the metadata for a resource. result = api_instance.get_user_metadata(user_id, resource_uri) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling MetadataApi->get_user_metadata: #{e}" end ``` @@ -68,13 +68,13 @@ Update the metadata for a resource. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::MetadataApi.new -body = SwaggerClient::Body.new # Body | Important: Data request object which contains properties identifying the data as well as the metadata itself. While there is limited access, the data saved here should be considered encrypted with best practices (Encrypted in Transit and Encrypted at Rest only). However, while Authress will to store and access in the data in a safe way, usage of this endpoint affirms this data must be application data and not user data. If there are explicit regulations or compliances regarding the data and how it should be saved here, this endpoint must not be used. That includes, but is not limited to--user personal data, data that is protected by GDPR and similar data protection regulations. +api_instance = AuthressSdk::MetadataApi.new +body = AuthressSdk::Body.new # Body | Important: Data request object which contains properties identifying the data as well as the metadata itself. While there is limited access, the data saved here should be considered encrypted with best practices (Encrypted in Transit and Encrypted at Rest only). However, while Authress will to store and access in the data in a safe way, usage of this endpoint affirms this data must be application data and not user data. If there are explicit regulations or compliances regarding the data and how it should be saved here, this endpoint must not be used. That includes, but is not limited to--user personal data, data that is protected by GDPR and similar data protection regulations. user_id = 'user_id_example' # String | The owner of the data. resource_uri = 'resource_uri_example' # String | The resource the data is attached to. @@ -83,7 +83,7 @@ begin #Update the metadata for a resource. result = api_instance.update_user_metadata(bodyuser_idresource_uri) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling MetadataApi->update_user_metadata: #{e}" end ``` diff --git a/docs/MetadataObject.md b/docs/MetadataObject.md index c17b16d..ad2851f 100644 --- a/docs/MetadataObject.md +++ b/docs/MetadataObject.md @@ -1,4 +1,4 @@ -# SwaggerClient::MetadataObject +# AuthressSdk::MetadataObject ## Properties Name | Type | Description | Notes diff --git a/docs/PermissionObject.md b/docs/PermissionObject.md index 3434d06..34b379d 100644 --- a/docs/PermissionObject.md +++ b/docs/PermissionObject.md @@ -1,4 +1,4 @@ -# SwaggerClient::PermissionObject +# AuthressSdk::PermissionObject ## Properties Name | Type | Description | Notes diff --git a/docs/PermissionResponse.md b/docs/PermissionResponse.md index baf87b8..ddae76c 100644 --- a/docs/PermissionResponse.md +++ b/docs/PermissionResponse.md @@ -1,4 +1,4 @@ -# SwaggerClient::PermissionResponse +# AuthressSdk::PermissionResponse ## Properties Name | Type | Description | Notes diff --git a/docs/ResourcePermission.md b/docs/ResourcePermission.md index ecb1d00..1d3beb0 100644 --- a/docs/ResourcePermission.md +++ b/docs/ResourcePermission.md @@ -1,4 +1,4 @@ -# SwaggerClient::ResourcePermission +# AuthressSdk::ResourcePermission ## Properties Name | Type | Description | Notes diff --git a/docs/ResourcePermissionCollection.md b/docs/ResourcePermissionCollection.md index a184aaf..b77fab3 100644 --- a/docs/ResourcePermissionCollection.md +++ b/docs/ResourcePermissionCollection.md @@ -1,4 +1,4 @@ -# SwaggerClient::ResourcePermissionCollection +# AuthressSdk::ResourcePermissionCollection ## Properties Name | Type | Description | Notes diff --git a/docs/ResourcePermissionCollectionLinks.md b/docs/ResourcePermissionCollectionLinks.md index afef04c..741f27d 100644 --- a/docs/ResourcePermissionCollectionLinks.md +++ b/docs/ResourcePermissionCollectionLinks.md @@ -1,4 +1,4 @@ -# SwaggerClient::ResourcePermissionCollectionLinks +# AuthressSdk::ResourcePermissionCollectionLinks ## Properties Name | Type | Description | Notes diff --git a/docs/ResourcePermissionCollectionLinksNext.md b/docs/ResourcePermissionCollectionLinksNext.md index 2f39565..7dc95c2 100644 --- a/docs/ResourcePermissionCollectionLinksNext.md +++ b/docs/ResourcePermissionCollectionLinksNext.md @@ -1,4 +1,4 @@ -# SwaggerClient::ResourcePermissionCollectionLinksNext +# AuthressSdk::ResourcePermissionCollectionLinksNext ## Properties Name | Type | Description | Notes diff --git a/docs/ResourcePermissionCollectionResources.md b/docs/ResourcePermissionCollectionResources.md index 9b4ccee..7b2e182 100644 --- a/docs/ResourcePermissionCollectionResources.md +++ b/docs/ResourcePermissionCollectionResources.md @@ -1,4 +1,4 @@ -# SwaggerClient::ResourcePermissionCollectionResources +# AuthressSdk::ResourcePermissionCollectionResources ## Properties Name | Type | Description | Notes diff --git a/docs/ResourcePermissionsApi.md b/docs/ResourcePermissionsApi.md index 017292d..252c171 100644 --- a/docs/ResourcePermissionsApi.md +++ b/docs/ResourcePermissionsApi.md @@ -1,4 +1,4 @@ -# SwaggerClient::ResourcePermissionsApi +# AuthressSdk::ResourcePermissionsApi All URIs are relative to */* @@ -19,12 +19,12 @@ Permissions can be set globally at a resource level. This will apply to all user ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ResourcePermissionsApi.new +api_instance = AuthressSdk::ResourcePermissionsApi.new resource_uri = 'resource_uri_example' # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed. @@ -32,7 +32,7 @@ begin #Get a resource permissions object. result = api_instance.get_resource_permissions(resource_uri) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ResourcePermissionsApi->get_resource_permissions: #{e}" end ``` @@ -68,12 +68,12 @@ Get the users that have explicit access to this resource. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ResourcePermissionsApi.new +api_instance = AuthressSdk::ResourcePermissionsApi.new resource_uri = 'resource_uri_example' # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed. opts = { limit: 20, # Integer | Max number of results to return @@ -84,7 +84,7 @@ begin #Get the users that have explicit access to this resource. result = api_instance.get_resource_users(resource_uri, opts) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ResourcePermissionsApi->get_resource_users: #{e}" end ``` @@ -122,18 +122,18 @@ Permissions can be set globally at a resource level. Lists any resources with a ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ResourcePermissionsApi.new +api_instance = AuthressSdk::ResourcePermissionsApi.new begin #List resource configurations. result = api_instance.get_resources p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ResourcePermissionsApi->get_resources: #{e}" end ``` @@ -166,20 +166,20 @@ Updates the global permissions on a resource. This applies to all users in an ac ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ResourcePermissionsApi.new -body = SwaggerClient::Body2.new # Body2 | The contents of the permission to set on the resource. Overwrites existing data. +api_instance = AuthressSdk::ResourcePermissionsApi.new +body = AuthressSdk::Body2.new # Body2 | The contents of the permission to set on the resource. Overwrites existing data. resource_uri = 'resource_uri_example' # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed. begin #Update a resource permissions object. api_instance.update_resource_permissions(bodyresource_uri) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ResourcePermissionsApi->update_resource_permissions: #{e}" end ``` diff --git a/docs/ResourceUsersCollection.md b/docs/ResourceUsersCollection.md index 0cb7e44..45e823a 100644 --- a/docs/ResourceUsersCollection.md +++ b/docs/ResourceUsersCollection.md @@ -1,4 +1,4 @@ -# SwaggerClient::ResourceUsersCollection +# AuthressSdk::ResourceUsersCollection ## Properties Name | Type | Description | Notes diff --git a/docs/Role.md b/docs/Role.md index 6ea3b22..9c7fee0 100644 --- a/docs/Role.md +++ b/docs/Role.md @@ -1,4 +1,4 @@ -# SwaggerClient::Role +# AuthressSdk::Role ## Properties Name | Type | Description | Notes diff --git a/docs/RolesApi.md b/docs/RolesApi.md index 90303b1..8a06f91 100644 --- a/docs/RolesApi.md +++ b/docs/RolesApi.md @@ -1,4 +1,4 @@ -# SwaggerClient::RolesApi +# AuthressSdk::RolesApi All URIs are relative to */* @@ -19,20 +19,20 @@ Creates a role with permissions.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling RolesApi->create_role: #{e}" end ``` @@ -68,19 +68,19 @@ Remove a role. If a record references the role, that record will not be modified ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::RolesApi.new +api_instance = AuthressSdk::RolesApi.new role_id = 'role_id_example' # String | The identifier of the role. begin #Deletes a role. api_instance.delete_role(role_id) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling RolesApi->delete_role: #{e}" end ``` @@ -116,12 +116,12 @@ Roles contain a list of permissions that will be applied to any user or resource ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::RolesApi.new +api_instance = AuthressSdk::RolesApi.new role_id = 'role_id_example' # String | The identifier of the role. @@ -129,7 +129,7 @@ begin #Get a role. result = api_instance.get_role(role_id) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling RolesApi->get_role: #{e}" end ``` @@ -165,13 +165,13 @@ Updates a role adding or removing permissions.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling RolesApi->update_role: #{e}" end ``` diff --git a/docs/ServiceClientsApi.md b/docs/ServiceClientsApi.md index 0c315e0..17489a0 100644 --- a/docs/ServiceClientsApi.md +++ b/docs/ServiceClientsApi.md @@ -1,4 +1,4 @@ -# SwaggerClient::ServiceClientsApi +# AuthressSdk::ServiceClientsApi All URIs are relative to */* @@ -22,20 +22,20 @@ Creates a service client to interact with Authress or any other service on behal ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ServiceClientsApi.new -body = SwaggerClient::Body10.new # Body10 | +api_instance = AuthressSdk::ServiceClientsApi.new +body = AuthressSdk::Body10.new # Body10 | begin #Create a new client. result = api_instance.create_client(body) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ServiceClientsApi->create_client: #{e}" end ``` @@ -71,12 +71,12 @@ Deletes an access key for a client prevent it from being used to authenticate wi ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ServiceClientsApi.new +api_instance = AuthressSdk::ServiceClientsApi.new client_id = 'client_id_example' # String | The unique identifier of the client. key_id = 'key_id_example' # String | The id of the access key to remove from the client. @@ -84,7 +84,7 @@ key_id = 'key_id_example' # String | The id of the access key to remove from the begin #Remove an access key for a client. api_instance.delete_access_key(client_id, key_id) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ServiceClientsApi->delete_access_key: #{e}" end ``` @@ -121,19 +121,19 @@ This deletes the service client.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling ServiceClientsApi->delete_client: #{e}" end ``` @@ -169,12 +169,12 @@ Returns all information related to client except for the private access keys. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ServiceClientsApi.new +api_instance = AuthressSdk::ServiceClientsApi.new client_id = 'client_id_example' # String | The unique identifier for the client. @@ -182,7 +182,7 @@ begin #Get a client. result = api_instance.get_client(client_id) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ServiceClientsApi->get_client: #{e}" end ``` @@ -218,18 +218,18 @@ Returns all clients that the user has access to in the account.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling ServiceClientsApi->get_clients: #{e}" end ``` @@ -262,12 +262,12 @@ Create a new access key for the client so that a service can authenticate with A ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::ServiceClientsApi.new +api_instance = AuthressSdk::ServiceClientsApi.new client_id = 'client_id_example' # String | The unique identifier of the client. @@ -275,7 +275,7 @@ begin #Request a new access key. result = api_instance.request_access_key(client_id) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling ServiceClientsApi->request_access_key: #{e}" end ``` @@ -311,13 +311,13 @@ Updates a client information.
e +rescue AuthressSdk::ApiError => e puts "Exception when calling ServiceClientsApi->update_client: #{e}" end ``` diff --git a/docs/Statement.md b/docs/Statement.md index f0045ea..b31fbb2 100644 --- a/docs/Statement.md +++ b/docs/Statement.md @@ -1,4 +1,4 @@ -# SwaggerClient::Statement +# AuthressSdk::Statement ## Properties Name | Type | Description | Notes diff --git a/docs/TokenRequest.md b/docs/TokenRequest.md index 4b510fa..df98402 100644 --- a/docs/TokenRequest.md +++ b/docs/TokenRequest.md @@ -1,4 +1,4 @@ -# SwaggerClient::TokenRequest +# AuthressSdk::TokenRequest ## Properties Name | Type | Description | Notes diff --git a/docs/User.md b/docs/User.md index bd349be..1b17722 100644 --- a/docs/User.md +++ b/docs/User.md @@ -1,4 +1,4 @@ -# SwaggerClient::User +# AuthressSdk::User ## Properties Name | Type | Description | Notes diff --git a/docs/UserPermissionsApi.md b/docs/UserPermissionsApi.md index de2db6b..9de226d 100644 --- a/docs/UserPermissionsApi.md +++ b/docs/UserPermissionsApi.md @@ -1,4 +1,4 @@ -# SwaggerClient::UserPermissionsApi +# AuthressSdk::UserPermissionsApi All URIs are relative to */* @@ -20,12 +20,12 @@ Check to see if a user has permissions to a resource. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::UserPermissionsApi.new +api_instance = AuthressSdk::UserPermissionsApi.new user_id = 'user_id_example' # String | The user to check permissions on resource_uri = 'resource_uri_example' # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed, the resource must be a full path, and permissions are not inherited by sub-resources. permission = 'permission_example' # String | Permission to check, '*' and scoped permissions can also be checked here. @@ -34,7 +34,7 @@ permission = 'permission_example' # String | Permission to check, '*' and scoped begin #Check to see if a user has permissions to a resource. api_instance.authorize_user(user_id, resource_uri, permission) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling UserPermissionsApi->authorize_user: #{e}" end ``` @@ -72,12 +72,12 @@ Disable a token. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::UserPermissionsApi.new +api_instance = AuthressSdk::UserPermissionsApi.new user_id = 'user_id_example' # String | The user to create an impersonation token for. token_id = 'token_id_example' # String | The relevant token identifier @@ -85,7 +85,7 @@ token_id = 'token_id_example' # String | The relevant token identifier begin #Disable a token. api_instance.disable_user_token(user_id, token_id) -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling UserPermissionsApi->disable_user_token: #{e}" end ``` @@ -122,12 +122,12 @@ Get the permissions a user has to a resource. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::UserPermissionsApi.new +api_instance = AuthressSdk::UserPermissionsApi.new user_id = 'user_id_example' # String | The user to check permissions on resource_uri = 'resource_uri_example' # String | The uri path of a resource to validate, must be URL encoded, uri segments are allowed. @@ -136,7 +136,7 @@ begin #Get the permissions a user has to a resource. result = api_instance.get_user_permissions_for_resource(user_id, resource_uri) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling UserPermissionsApi->get_user_permissions_for_resource: #{e}" end ``` @@ -173,12 +173,12 @@ Get the resources a user has to permission to. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::UserPermissionsApi.new +api_instance = AuthressSdk::UserPermissionsApi.new user_id = 'user_id_example' # String | The user to check permissions on opts = { resource_uri: '*', # String | The top level uri path of a resource to query for. Will only match explicit or collection resource children. Will not partial match resource names. @@ -191,7 +191,7 @@ begin #Get the resources a user has to permission to. result = api_instance.get_user_resources(user_id, opts) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling UserPermissionsApi->get_user_resources: #{e}" end ``` @@ -231,13 +231,13 @@ Request a user token with additional configuration. ### Example ```ruby # load the gem -require 'swagger_client' +require 'authress_sdk' # setup authorization -SwaggerClient.configure do |config| +AuthressSdk.configure do |config| end -api_instance = SwaggerClient::UserPermissionsApi.new -body = SwaggerClient::Body1.new # Body1 | The contents of the permission to set on the token. Will be used instead of the users or clients full permissions. Cannot include permissions that the user or client do not have. +api_instance = AuthressSdk::UserPermissionsApi.new +body = AuthressSdk::Body1.new # Body1 | The contents of the permission to set on the token. Will be used instead of the users or clients full permissions. Cannot include permissions that the user or client do not have. user_id = 'user_id_example' # String | The user to create an impersonation token for. @@ -245,7 +245,7 @@ begin #Request a user token with additional configuration. result = api_instance.request_user_token(bodyuser_id) p result -rescue SwaggerClient::ApiError => e +rescue AuthressSdk::ApiError => e puts "Exception when calling UserPermissionsApi->request_user_token: #{e}" end ``` diff --git a/docs/UserResources.md b/docs/UserResources.md index e3fd911..b57c836 100644 --- a/docs/UserResources.md +++ b/docs/UserResources.md @@ -1,4 +1,4 @@ -# SwaggerClient::UserResources +# AuthressSdk::UserResources ## Properties Name | Type | Description | Notes diff --git a/docs/UserResourcesResources.md b/docs/UserResourcesResources.md index 5e3c1dd..9f40da8 100644 --- a/docs/UserResourcesResources.md +++ b/docs/UserResourcesResources.md @@ -1,4 +1,4 @@ -# SwaggerClient::UserResourcesResources +# AuthressSdk::UserResourcesResources ## Properties Name | Type | Description | Notes diff --git a/docs/UserToken.md b/docs/UserToken.md index e33221f..fb93c1d 100644 --- a/docs/UserToken.md +++ b/docs/UserToken.md @@ -1,4 +1,4 @@ -# SwaggerClient::UserToken +# AuthressSdk::UserToken ## Properties Name | Type | Description | Notes diff --git a/docs/UserTokenLinks.md b/docs/UserTokenLinks.md index b34cdac..a7d7c23 100644 --- a/docs/UserTokenLinks.md +++ b/docs/UserTokenLinks.md @@ -1,4 +1,4 @@ -# SwaggerClient::UserTokenLinks +# AuthressSdk::UserTokenLinks ## Properties Name | Type | Description | Notes diff --git a/docs/UserTokenLinksSelf.md b/docs/UserTokenLinksSelf.md index 86a4bb3..6cdf6ca 100644 --- a/docs/UserTokenLinksSelf.md +++ b/docs/UserTokenLinksSelf.md @@ -1,4 +1,4 @@ -# SwaggerClient::UserTokenLinksSelf +# AuthressSdk::UserTokenLinksSelf ## Properties Name | Type | Description | Notes diff --git a/docs/V1clientsOptions.md b/docs/V1clientsOptions.md index 4d016f5..68f6c63 100644 --- a/docs/V1clientsOptions.md +++ b/docs/V1clientsOptions.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1clientsOptions +# AuthressSdk::V1clientsOptions ## Properties Name | Type | Description | Notes diff --git a/docs/V1recordsAccount.md b/docs/V1recordsAccount.md index 7d3ad1f..9d923f0 100644 --- a/docs/V1recordsAccount.md +++ b/docs/V1recordsAccount.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1recordsAccount +# AuthressSdk::V1recordsAccount ## Properties Name | Type | Description | Notes diff --git a/docs/V1recordsLinks.md b/docs/V1recordsLinks.md index 12117b2..963bf1e 100644 --- a/docs/V1recordsLinks.md +++ b/docs/V1recordsLinks.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1recordsLinks +# AuthressSdk::V1recordsLinks ## Properties Name | Type | Description | Notes diff --git a/docs/V1recordsLinksSelf.md b/docs/V1recordsLinksSelf.md index 67ff2fd..b7401f8 100644 --- a/docs/V1recordsLinksSelf.md +++ b/docs/V1recordsLinksSelf.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1recordsLinksSelf +# AuthressSdk::V1recordsLinksSelf ## Properties Name | Type | Description | Notes diff --git a/docs/V1recordsUsers.md b/docs/V1recordsUsers.md index 205e156..1e4b631 100644 --- a/docs/V1recordsUsers.md +++ b/docs/V1recordsUsers.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1recordsUsers +# AuthressSdk::V1recordsUsers ## Properties Name | Type | Description | Notes diff --git a/docs/V1resourcesresourceUriPermissions.md b/docs/V1resourcesresourceUriPermissions.md index d0082ad..39eabde 100644 --- a/docs/V1resourcesresourceUriPermissions.md +++ b/docs/V1resourcesresourceUriPermissions.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1resourcesresourceUriPermissions +# AuthressSdk::V1resourcesresourceUriPermissions ## Properties Name | Type | Description | Notes diff --git a/docs/V1rolesPermissions.md b/docs/V1rolesPermissions.md index 6c62bd2..d860a38 100644 --- a/docs/V1rolesPermissions.md +++ b/docs/V1rolesPermissions.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1rolesPermissions +# AuthressSdk::V1rolesPermissions ## Properties Name | Type | Description | Notes diff --git a/docs/V1usersuserIdresourcesresourceUrimetadataAccount.md b/docs/V1usersuserIdresourcesresourceUrimetadataAccount.md index 3de99e0..67dc84e 100644 --- a/docs/V1usersuserIdresourcesresourceUrimetadataAccount.md +++ b/docs/V1usersuserIdresourcesresourceUrimetadataAccount.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1usersuserIdresourcesresourceUrimetadataAccount +# AuthressSdk::V1usersuserIdresourcesresourceUrimetadataAccount ## Properties Name | Type | Description | Notes diff --git a/docs/V1usersuserIdtokensResources.md b/docs/V1usersuserIdtokensResources.md index dbb9c7e..411b6a3 100644 --- a/docs/V1usersuserIdtokensResources.md +++ b/docs/V1usersuserIdtokensResources.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1usersuserIdtokensResources +# AuthressSdk::V1usersuserIdtokensResources ## Properties Name | Type | Description | Notes diff --git a/docs/V1usersuserIdtokensStatements.md b/docs/V1usersuserIdtokensStatements.md index 4d3351e..911a126 100644 --- a/docs/V1usersuserIdtokensStatements.md +++ b/docs/V1usersuserIdtokensStatements.md @@ -1,4 +1,4 @@ -# SwaggerClient::V1usersuserIdtokensStatements +# AuthressSdk::V1usersuserIdtokensStatements ## Properties Name | Type | Description | Notes diff --git a/lib/authress_sdk.rb b/lib/authress_sdk.rb new file mode 100644 index 0000000..04e1e25 --- /dev/null +++ b/lib/authress_sdk.rb @@ -0,0 +1,18 @@ +=begin + +=end + +Dir["#{File.expand_path(File.dirname(__FILE__))}/**/*.rb"].each{|f| require f} + +module AuthressSdk + class << self + # Customize default settings for the SDK using block. + # AuthressSdk.configure do |config| + # config.username = "xxx" + # config.password = "xxx" + # end + def configure + AuthressClient.default + end + end +end diff --git a/lib/swagger_client/api/access_records_api.rb b/lib/authress_sdk/api/access_records_api.rb similarity index 72% rename from lib/swagger_client/api/access_records_api.rb rename to lib/authress_sdk/api/access_records_api.rb index 51bf145..1c91a4f 100644 --- a/lib/swagger_client/api/access_records_api.rb +++ b/lib/authress_sdk/api/access_records_api.rb @@ -1,20 +1,13 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end -module SwaggerClient +module AuthressSdk class AccessRecordsApi - attr_accessor :api_client + attr_accessor :authress_client - def initialize(api_client = ApiClient.default) - @api_client = api_client + def initialize(authress_client = AuthressClient.default) + @authress_client = authress_client end # Claim a resource by an allowed user. # Claim a resource by allowing a user to pick an identifier and receive admin access to that resource if it hasn't already been claimed. This only works for resources specifically marked as CLAIM. The result will be a new access record listing that user as the admin for this resource. The resourceUri will be appended to the collection resource uri using a '/' (forward slash) automatically.
RESOURCE CLAIM: {resourceUri} or DELEGATE *: {resourceUri} @@ -32,11 +25,11 @@ def create_claim(body, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers def create_claim_with_http_info(body, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.create_claim ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.create_claim ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling AccessRecordsApi.create_claim" end # resource path @@ -48,20 +41,20 @@ def create_claim_with_http_info(body, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'Object' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -69,8 +62,8 @@ def create_claim_with_http_info(body, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#create_claim\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#create_claim\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -90,11 +83,11 @@ def create_invite(body, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def create_invite_with_http_info(body, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.create_invite ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.create_invite ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling AccessRecordsApi.create_invite" end # resource path @@ -106,18 +99,18 @@ def create_invite_with_http_info(body, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -125,8 +118,8 @@ def create_invite_with_http_info(body, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#create_invite\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#create_invite\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -146,11 +139,11 @@ def create_record(body, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2008, Integer, Hash)>] InlineResponse2008 data, response status code and response headers def create_record_with_http_info(body, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.create_record ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.create_record ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling AccessRecordsApi.create_record" end # resource path @@ -162,20 +155,20 @@ def create_record_with_http_info(body, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse2008' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -183,8 +176,8 @@ def create_record_with_http_info(body, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#create_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#create_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -204,11 +197,11 @@ def delete_invite(invite_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def delete_invite_with_http_info(invite_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.delete_invite ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.delete_invite ...' end # verify the required parameter 'invite_id' is set - if @api_client.config.client_side_validation && invite_id.nil? + if @authress_client.config.client_side_validation && invite_id.nil? fail ArgumentError, "Missing the required parameter 'invite_id' when calling AccessRecordsApi.delete_invite" end # resource path @@ -229,7 +222,7 @@ def delete_invite_with_http_info(invite_id, opts = {}) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:DELETE, local_var_path, + data, status_code, headers = @authress_client.call_api(:DELETE, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -237,8 +230,8 @@ def delete_invite_with_http_info(invite_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#delete_invite\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#delete_invite\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -258,11 +251,11 @@ def delete_record(record_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def delete_record_with_http_info(record_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.delete_record ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.delete_record ...' end # verify the required parameter 'record_id' is set - if @api_client.config.client_side_validation && record_id.nil? + if @authress_client.config.client_side_validation && record_id.nil? fail ArgumentError, "Missing the required parameter 'record_id' when calling AccessRecordsApi.delete_record" end # resource path @@ -283,7 +276,7 @@ def delete_record_with_http_info(record_id, opts = {}) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:DELETE, local_var_path, + data, status_code, headers = @authress_client.call_api(:DELETE, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -291,8 +284,8 @@ def delete_record_with_http_info(record_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#delete_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#delete_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -312,11 +305,11 @@ def get_record(record_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2008, Integer, Hash)>] InlineResponse2008 data, response status code and response headers def get_record_with_http_info(record_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.get_record ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.get_record ...' end # verify the required parameter 'record_id' is set - if @api_client.config.client_side_validation && record_id.nil? + if @authress_client.config.client_side_validation && record_id.nil? fail ArgumentError, "Missing the required parameter 'record_id' when calling AccessRecordsApi.get_record" end # resource path @@ -328,7 +321,7 @@ def get_record_with_http_info(record_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -339,7 +332,7 @@ def get_record_with_http_info(record_id, opts = {}) return_type = opts[:return_type] || 'InlineResponse2008' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -347,8 +340,8 @@ def get_record_with_http_info(record_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#get_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#get_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -374,10 +367,10 @@ def get_records(opts = {}) # @option opts [String] :status Filter records by their current status. # @return [Array<(InlineResponse2007, Integer, Hash)>] InlineResponse2007 data, response status code and response headers def get_records_with_http_info(opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.get_records ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.get_records ...' end - if @api_client.config.client_side_validation && opts[:'status'] && !['ACTIVE', 'DELETED'].include?(opts[:'status']) + if @authress_client.config.client_side_validation && opts[:'status'] && !['ACTIVE', 'DELETED'].include?(opts[:'status']) fail ArgumentError, 'invalid value for "status", must be one of ACTIVE, DELETED' end # resource path @@ -393,7 +386,7 @@ def get_records_with_http_info(opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -404,7 +397,7 @@ def get_records_with_http_info(opts = {}) return_type = opts[:return_type] || 'InlineResponse2007' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -412,8 +405,8 @@ def get_records_with_http_info(opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#get_records\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#get_records\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -433,11 +426,11 @@ def respond_to_invite(invite_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2009, Integer, Hash)>] InlineResponse2009 data, response status code and response headers def respond_to_invite_with_http_info(invite_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.respond_to_invite ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.respond_to_invite ...' end # verify the required parameter 'invite_id' is set - if @api_client.config.client_side_validation && invite_id.nil? + if @authress_client.config.client_side_validation && invite_id.nil? fail ArgumentError, "Missing the required parameter 'invite_id' when calling AccessRecordsApi.respond_to_invite" end # resource path @@ -449,7 +442,7 @@ def respond_to_invite_with_http_info(invite_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -460,7 +453,7 @@ def respond_to_invite_with_http_info(invite_id, opts = {}) return_type = opts[:return_type] || 'InlineResponse2009' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:PATCH, local_var_path, + data, status_code, headers = @authress_client.call_api(:PATCH, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -468,8 +461,8 @@ def respond_to_invite_with_http_info(invite_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#respond_to_invite\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#respond_to_invite\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -491,15 +484,15 @@ def update_record(body, record_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2008, Integer, Hash)>] InlineResponse2008 data, response status code and response headers def update_record_with_http_info(body, record_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccessRecordsApi.update_record ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccessRecordsApi.update_record ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling AccessRecordsApi.update_record" end # verify the required parameter 'record_id' is set - if @api_client.config.client_side_validation && record_id.nil? + if @authress_client.config.client_side_validation && record_id.nil? fail ArgumentError, "Missing the required parameter 'record_id' when calling AccessRecordsApi.update_record" end # resource path @@ -511,20 +504,20 @@ def update_record_with_http_info(body, record_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse2008' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:PUT, local_var_path, + data, status_code, headers = @authress_client.call_api(:PUT, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -532,8 +525,8 @@ def update_record_with_http_info(body, record_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccessRecordsApi#update_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccessRecordsApi#update_record\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end diff --git a/lib/swagger_client/api/accounts_api.rb b/lib/authress_sdk/api/accounts_api.rb similarity index 61% rename from lib/swagger_client/api/accounts_api.rb rename to lib/authress_sdk/api/accounts_api.rb index ead3cea..f3aefad 100644 --- a/lib/swagger_client/api/accounts_api.rb +++ b/lib/authress_sdk/api/accounts_api.rb @@ -1,20 +1,13 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end -module SwaggerClient +module AuthressSdk class AccountsApi - attr_accessor :api_client + attr_accessor :authress_client - def initialize(api_client = ApiClient.default) - @api_client = api_client + def initialize(authress_client = AuthressClient.default) + @authress_client = authress_client end # Get account information. # Includes the original configuration information.
READ: Authress:Configuration @@ -32,11 +25,11 @@ def get_account(account_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2009, Integer, Hash)>] InlineResponse2009 data, response status code and response headers def get_account_with_http_info(account_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccountsApi.get_account ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccountsApi.get_account ...' end # verify the required parameter 'account_id' is set - if @api_client.config.client_side_validation && account_id.nil? + if @authress_client.config.client_side_validation && account_id.nil? fail ArgumentError, "Missing the required parameter 'account_id' when calling AccountsApi.get_account" end # resource path @@ -48,7 +41,7 @@ def get_account_with_http_info(account_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -59,7 +52,7 @@ def get_account_with_http_info(account_id, opts = {}) return_type = opts[:return_type] || 'InlineResponse2009' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -67,8 +60,8 @@ def get_account_with_http_info(account_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccountsApi#get_account\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccountsApi#get_account\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -86,8 +79,8 @@ def get_account_identities(opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20012, Integer, Hash)>] InlineResponse20012 data, response status code and response headers def get_account_identities_with_http_info(opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccountsApi.get_account_identities ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccountsApi.get_account_identities ...' end # resource path local_var_path = '/v1/identities' @@ -98,7 +91,7 @@ def get_account_identities_with_http_info(opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -109,7 +102,7 @@ def get_account_identities_with_http_info(opts = {}) return_type = opts[:return_type] || 'InlineResponse20012' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -117,8 +110,8 @@ def get_account_identities_with_http_info(opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccountsApi#get_account_identities\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccountsApi#get_account_identities\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -136,8 +129,8 @@ def get_accounts(opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20011, Integer, Hash)>] InlineResponse20011 data, response status code and response headers def get_accounts_with_http_info(opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccountsApi.get_accounts ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccountsApi.get_accounts ...' end # resource path local_var_path = '/v1/accounts' @@ -148,7 +141,7 @@ def get_accounts_with_http_info(opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -159,7 +152,7 @@ def get_accounts_with_http_info(opts = {}) return_type = opts[:return_type] || 'InlineResponse20011' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -167,8 +160,8 @@ def get_accounts_with_http_info(opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccountsApi#get_accounts\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccountsApi#get_accounts\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -188,11 +181,11 @@ def link_identity(body, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def link_identity_with_http_info(body, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: AccountsApi.link_identity ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: AccountsApi.link_identity ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling AccountsApi.link_identity" end # resource path @@ -204,18 +197,18 @@ def link_identity_with_http_info(body, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -223,8 +216,8 @@ def link_identity_with_http_info(body, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: AccountsApi#link_identity\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: AccountsApi#link_identity\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end diff --git a/lib/swagger_client/api/metadata_api.rb b/lib/authress_sdk/api/metadata_api.rb similarity index 67% rename from lib/swagger_client/api/metadata_api.rb rename to lib/authress_sdk/api/metadata_api.rb index 9224e6d..27ebd2e 100644 --- a/lib/swagger_client/api/metadata_api.rb +++ b/lib/authress_sdk/api/metadata_api.rb @@ -1,20 +1,13 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end -module SwaggerClient +module AuthressSdk class MetadataApi - attr_accessor :api_client + attr_accessor :authress_client - def initialize(api_client = ApiClient.default) - @api_client = api_client + def initialize(authress_client = AuthressClient.default) + @authress_client = authress_client end # Get the metadata for a resource. # Billable Metadata is partitioned by the resource owner, and each can store independent data for a resource. This data is only accessible by identity provider tokens which specify the sub property and by service clients which have the grantMetadataAccess property.
READ: Authress:MetadataResources/{resourceUri} @@ -34,15 +27,15 @@ def get_user_metadata(user_id, resource_uri, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2001, Integer, Hash)>] InlineResponse2001 data, response status code and response headers def get_user_metadata_with_http_info(user_id, resource_uri, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: MetadataApi.get_user_metadata ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: MetadataApi.get_user_metadata ...' end # verify the required parameter 'user_id' is set - if @api_client.config.client_side_validation && user_id.nil? + if @authress_client.config.client_side_validation && user_id.nil? fail ArgumentError, "Missing the required parameter 'user_id' when calling MetadataApi.get_user_metadata" end # verify the required parameter 'resource_uri' is set - if @api_client.config.client_side_validation && resource_uri.nil? + if @authress_client.config.client_side_validation && resource_uri.nil? fail ArgumentError, "Missing the required parameter 'resource_uri' when calling MetadataApi.get_user_metadata" end # resource path @@ -54,7 +47,7 @@ def get_user_metadata_with_http_info(user_id, resource_uri, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -65,7 +58,7 @@ def get_user_metadata_with_http_info(user_id, resource_uri, opts = {}) return_type = opts[:return_type] || 'InlineResponse2001' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -73,8 +66,8 @@ def get_user_metadata_with_http_info(user_id, resource_uri, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: MetadataApi#get_user_metadata\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: MetadataApi#get_user_metadata\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -98,19 +91,19 @@ def update_user_metadata(body, user_id, resource_uri, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2001, Integer, Hash)>] InlineResponse2001 data, response status code and response headers def update_user_metadata_with_http_info(body, user_id, resource_uri, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: MetadataApi.update_user_metadata ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: MetadataApi.update_user_metadata ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling MetadataApi.update_user_metadata" end # verify the required parameter 'user_id' is set - if @api_client.config.client_side_validation && user_id.nil? + if @authress_client.config.client_side_validation && user_id.nil? fail ArgumentError, "Missing the required parameter 'user_id' when calling MetadataApi.update_user_metadata" end # verify the required parameter 'resource_uri' is set - if @api_client.config.client_side_validation && resource_uri.nil? + if @authress_client.config.client_side_validation && resource_uri.nil? fail ArgumentError, "Missing the required parameter 'resource_uri' when calling MetadataApi.update_user_metadata" end # resource path @@ -122,20 +115,20 @@ def update_user_metadata_with_http_info(body, user_id, resource_uri, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse2001' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:PUT, local_var_path, + data, status_code, headers = @authress_client.call_api(:PUT, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -143,8 +136,8 @@ def update_user_metadata_with_http_info(body, user_id, resource_uri, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: MetadataApi#update_user_metadata\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: MetadataApi#update_user_metadata\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end diff --git a/lib/swagger_client/api/resource_permissions_api.rb b/lib/authress_sdk/api/resource_permissions_api.rb similarity index 68% rename from lib/swagger_client/api/resource_permissions_api.rb rename to lib/authress_sdk/api/resource_permissions_api.rb index 6657131..53c130e 100644 --- a/lib/swagger_client/api/resource_permissions_api.rb +++ b/lib/authress_sdk/api/resource_permissions_api.rb @@ -1,20 +1,13 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end -module SwaggerClient +module AuthressSdk class ResourcePermissionsApi - attr_accessor :api_client + attr_accessor :authress_client - def initialize(api_client = ApiClient.default) - @api_client = api_client + def initialize(authress_client = AuthressClient.default) + @authress_client = authress_client end # Get a resource permissions object. # Permissions can be set globally at a resource level. This will apply to all users in an account.
GRANT *: Authress:ResourcePermissions/{resourceUri} @@ -32,11 +25,11 @@ def get_resource_permissions(resource_uri, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2005, Integer, Hash)>] InlineResponse2005 data, response status code and response headers def get_resource_permissions_with_http_info(resource_uri, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ResourcePermissionsApi.get_resource_permissions ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ResourcePermissionsApi.get_resource_permissions ...' end # verify the required parameter 'resource_uri' is set - if @api_client.config.client_side_validation && resource_uri.nil? + if @authress_client.config.client_side_validation && resource_uri.nil? fail ArgumentError, "Missing the required parameter 'resource_uri' when calling ResourcePermissionsApi.get_resource_permissions" end # resource path @@ -48,7 +41,7 @@ def get_resource_permissions_with_http_info(resource_uri, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -59,7 +52,7 @@ def get_resource_permissions_with_http_info(resource_uri, opts = {}) return_type = opts[:return_type] || 'InlineResponse2005' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -67,8 +60,8 @@ def get_resource_permissions_with_http_info(resource_uri, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ResourcePermissionsApi#get_resource_permissions\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ResourcePermissionsApi#get_resource_permissions\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -92,11 +85,11 @@ def get_resource_users(resource_uri, opts = {}) # @option opts [String] :cursor Continuation cursor for paging (will automatically be set) # @return [Array<(InlineResponse2006, Integer, Hash)>] InlineResponse2006 data, response status code and response headers def get_resource_users_with_http_info(resource_uri, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ResourcePermissionsApi.get_resource_users ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ResourcePermissionsApi.get_resource_users ...' end # verify the required parameter 'resource_uri' is set - if @api_client.config.client_side_validation && resource_uri.nil? + if @authress_client.config.client_side_validation && resource_uri.nil? fail ArgumentError, "Missing the required parameter 'resource_uri' when calling ResourcePermissionsApi.get_resource_users" end # resource path @@ -110,7 +103,7 @@ def get_resource_users_with_http_info(resource_uri, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -121,7 +114,7 @@ def get_resource_users_with_http_info(resource_uri, opts = {}) return_type = opts[:return_type] || 'InlineResponse2006' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -129,8 +122,8 @@ def get_resource_users_with_http_info(resource_uri, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ResourcePermissionsApi#get_resource_users\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ResourcePermissionsApi#get_resource_users\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -148,8 +141,8 @@ def get_resources(opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2004, Integer, Hash)>] InlineResponse2004 data, response status code and response headers def get_resources_with_http_info(opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ResourcePermissionsApi.get_resources ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ResourcePermissionsApi.get_resources ...' end # resource path local_var_path = '/v1/resources' @@ -160,7 +153,7 @@ def get_resources_with_http_info(opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -171,7 +164,7 @@ def get_resources_with_http_info(opts = {}) return_type = opts[:return_type] || 'InlineResponse2004' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -179,8 +172,8 @@ def get_resources_with_http_info(opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ResourcePermissionsApi#get_resources\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ResourcePermissionsApi#get_resources\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -202,15 +195,15 @@ def update_resource_permissions(body, resource_uri, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def update_resource_permissions_with_http_info(body, resource_uri, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ResourcePermissionsApi.update_resource_permissions ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ResourcePermissionsApi.update_resource_permissions ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling ResourcePermissionsApi.update_resource_permissions" end # verify the required parameter 'resource_uri' is set - if @api_client.config.client_side_validation && resource_uri.nil? + if @authress_client.config.client_side_validation && resource_uri.nil? fail ArgumentError, "Missing the required parameter 'resource_uri' when calling ResourcePermissionsApi.update_resource_permissions" end # resource path @@ -222,18 +215,18 @@ def update_resource_permissions_with_http_info(body, resource_uri, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:PUT, local_var_path, + data, status_code, headers = @authress_client.call_api(:PUT, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -241,8 +234,8 @@ def update_resource_permissions_with_http_info(body, resource_uri, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ResourcePermissionsApi#update_resource_permissions\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ResourcePermissionsApi#update_resource_permissions\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end diff --git a/lib/swagger_client/api/roles_api.rb b/lib/authress_sdk/api/roles_api.rb similarity index 61% rename from lib/swagger_client/api/roles_api.rb rename to lib/authress_sdk/api/roles_api.rb index 07da34f..998e2fb 100644 --- a/lib/swagger_client/api/roles_api.rb +++ b/lib/authress_sdk/api/roles_api.rb @@ -1,20 +1,13 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end -module SwaggerClient +module AuthressSdk class RolesApi - attr_accessor :api_client + attr_accessor :authress_client - def initialize(api_client = ApiClient.default) - @api_client = api_client + def initialize(authress_client = AuthressClient.default) + @authress_client = authress_client end # Create a role. # Creates a role with permissions.
CREATE: Authress:Roles @@ -32,11 +25,11 @@ def create_role(body, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20010, Integer, Hash)>] InlineResponse20010 data, response status code and response headers def create_role_with_http_info(body, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: RolesApi.create_role ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: RolesApi.create_role ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling RolesApi.create_role" end # resource path @@ -48,20 +41,20 @@ def create_role_with_http_info(body, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse20010' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -69,8 +62,8 @@ def create_role_with_http_info(body, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: RolesApi#create_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: RolesApi#create_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -90,11 +83,11 @@ def delete_role(role_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def delete_role_with_http_info(role_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: RolesApi.delete_role ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: RolesApi.delete_role ...' end # verify the required parameter 'role_id' is set - if @api_client.config.client_side_validation && role_id.nil? + if @authress_client.config.client_side_validation && role_id.nil? fail ArgumentError, "Missing the required parameter 'role_id' when calling RolesApi.delete_role" end # resource path @@ -115,7 +108,7 @@ def delete_role_with_http_info(role_id, opts = {}) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:DELETE, local_var_path, + data, status_code, headers = @authress_client.call_api(:DELETE, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -123,8 +116,8 @@ def delete_role_with_http_info(role_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: RolesApi#delete_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: RolesApi#delete_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -144,11 +137,11 @@ def get_role(role_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20010, Integer, Hash)>] InlineResponse20010 data, response status code and response headers def get_role_with_http_info(role_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: RolesApi.get_role ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: RolesApi.get_role ...' end # verify the required parameter 'role_id' is set - if @api_client.config.client_side_validation && role_id.nil? + if @authress_client.config.client_side_validation && role_id.nil? fail ArgumentError, "Missing the required parameter 'role_id' when calling RolesApi.get_role" end # resource path @@ -160,7 +153,7 @@ def get_role_with_http_info(role_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -171,7 +164,7 @@ def get_role_with_http_info(role_id, opts = {}) return_type = opts[:return_type] || 'InlineResponse20010' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -179,8 +172,8 @@ def get_role_with_http_info(role_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: RolesApi#get_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: RolesApi#get_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -202,15 +195,15 @@ def update_role(body, role_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20010, Integer, Hash)>] InlineResponse20010 data, response status code and response headers def update_role_with_http_info(body, role_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: RolesApi.update_role ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: RolesApi.update_role ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling RolesApi.update_role" end # verify the required parameter 'role_id' is set - if @api_client.config.client_side_validation && role_id.nil? + if @authress_client.config.client_side_validation && role_id.nil? fail ArgumentError, "Missing the required parameter 'role_id' when calling RolesApi.update_role" end # resource path @@ -222,20 +215,20 @@ def update_role_with_http_info(body, role_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse20010' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:PUT, local_var_path, + data, status_code, headers = @authress_client.call_api(:PUT, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -243,8 +236,8 @@ def update_role_with_http_info(body, role_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: RolesApi#update_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: RolesApi#update_role\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end diff --git a/lib/swagger_client/api/service_clients_api.rb b/lib/authress_sdk/api/service_clients_api.rb similarity index 69% rename from lib/swagger_client/api/service_clients_api.rb rename to lib/authress_sdk/api/service_clients_api.rb index 2ac6829..0931119 100644 --- a/lib/swagger_client/api/service_clients_api.rb +++ b/lib/authress_sdk/api/service_clients_api.rb @@ -1,20 +1,13 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end -module SwaggerClient +module AuthressSdk class ServiceClientsApi - attr_accessor :api_client + attr_accessor :authress_client - def initialize(api_client = ApiClient.default) - @api_client = api_client + def initialize(authress_client = AuthressClient.default) + @authress_client = authress_client end # Create a new client. # Creates a service client to interact with Authress or any other service on behalf of users. Each client has secret private keys used to authenticate with Authress. To use service clients created through other mechanisms, skip creating a client and create access records with the client identifier.
CREATE: Authress:ServiceClients or RESOURCE CLAIM: Authress:ServiceClients @@ -32,11 +25,11 @@ def create_client(body, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20014, Integer, Hash)>] InlineResponse20014 data, response status code and response headers def create_client_with_http_info(body, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ServiceClientsApi.create_client ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ServiceClientsApi.create_client ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling ServiceClientsApi.create_client" end # resource path @@ -48,20 +41,20 @@ def create_client_with_http_info(body, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse20014' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -69,8 +62,8 @@ def create_client_with_http_info(body, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ServiceClientsApi#create_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ServiceClientsApi#create_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -92,15 +85,15 @@ def delete_access_key(client_id, key_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def delete_access_key_with_http_info(client_id, key_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ServiceClientsApi.delete_access_key ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ServiceClientsApi.delete_access_key ...' end # verify the required parameter 'client_id' is set - if @api_client.config.client_side_validation && client_id.nil? + if @authress_client.config.client_side_validation && client_id.nil? fail ArgumentError, "Missing the required parameter 'client_id' when calling ServiceClientsApi.delete_access_key" end # verify the required parameter 'key_id' is set - if @api_client.config.client_side_validation && key_id.nil? + if @authress_client.config.client_side_validation && key_id.nil? fail ArgumentError, "Missing the required parameter 'key_id' when calling ServiceClientsApi.delete_access_key" end # resource path @@ -121,7 +114,7 @@ def delete_access_key_with_http_info(client_id, key_id, opts = {}) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:DELETE, local_var_path, + data, status_code, headers = @authress_client.call_api(:DELETE, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -129,8 +122,8 @@ def delete_access_key_with_http_info(client_id, key_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ServiceClientsApi#delete_access_key\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ServiceClientsApi#delete_access_key\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -150,11 +143,11 @@ def delete_client(client_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def delete_client_with_http_info(client_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ServiceClientsApi.delete_client ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ServiceClientsApi.delete_client ...' end # verify the required parameter 'client_id' is set - if @api_client.config.client_side_validation && client_id.nil? + if @authress_client.config.client_side_validation && client_id.nil? fail ArgumentError, "Missing the required parameter 'client_id' when calling ServiceClientsApi.delete_client" end # resource path @@ -175,7 +168,7 @@ def delete_client_with_http_info(client_id, opts = {}) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:DELETE, local_var_path, + data, status_code, headers = @authress_client.call_api(:DELETE, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -183,8 +176,8 @@ def delete_client_with_http_info(client_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ServiceClientsApi#delete_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ServiceClientsApi#delete_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -204,11 +197,11 @@ def get_client(client_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20014, Integer, Hash)>] InlineResponse20014 data, response status code and response headers def get_client_with_http_info(client_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ServiceClientsApi.get_client ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ServiceClientsApi.get_client ...' end # verify the required parameter 'client_id' is set - if @api_client.config.client_side_validation && client_id.nil? + if @authress_client.config.client_side_validation && client_id.nil? fail ArgumentError, "Missing the required parameter 'client_id' when calling ServiceClientsApi.get_client" end # resource path @@ -220,7 +213,7 @@ def get_client_with_http_info(client_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -231,7 +224,7 @@ def get_client_with_http_info(client_id, opts = {}) return_type = opts[:return_type] || 'InlineResponse20014' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -239,8 +232,8 @@ def get_client_with_http_info(client_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ServiceClientsApi#get_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ServiceClientsApi#get_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -258,8 +251,8 @@ def get_clients(opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20013, Integer, Hash)>] InlineResponse20013 data, response status code and response headers def get_clients_with_http_info(opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ServiceClientsApi.get_clients ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ServiceClientsApi.get_clients ...' end # resource path local_var_path = '/v1/clients' @@ -270,7 +263,7 @@ def get_clients_with_http_info(opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -281,7 +274,7 @@ def get_clients_with_http_info(opts = {}) return_type = opts[:return_type] || 'InlineResponse20013' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -289,8 +282,8 @@ def get_clients_with_http_info(opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ServiceClientsApi#get_clients\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ServiceClientsApi#get_clients\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -310,11 +303,11 @@ def request_access_key(client_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20015, Integer, Hash)>] InlineResponse20015 data, response status code and response headers def request_access_key_with_http_info(client_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ServiceClientsApi.request_access_key ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ServiceClientsApi.request_access_key ...' end # verify the required parameter 'client_id' is set - if @api_client.config.client_side_validation && client_id.nil? + if @authress_client.config.client_side_validation && client_id.nil? fail ArgumentError, "Missing the required parameter 'client_id' when calling ServiceClientsApi.request_access_key" end # resource path @@ -326,7 +319,7 @@ def request_access_key_with_http_info(client_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -337,7 +330,7 @@ def request_access_key_with_http_info(client_id, opts = {}) return_type = opts[:return_type] || 'InlineResponse20015' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -345,8 +338,8 @@ def request_access_key_with_http_info(client_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ServiceClientsApi#request_access_key\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ServiceClientsApi#request_access_key\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -368,15 +361,15 @@ def update_client(body, client_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse20014, Integer, Hash)>] InlineResponse20014 data, response status code and response headers def update_client_with_http_info(body, client_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: ServiceClientsApi.update_client ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: ServiceClientsApi.update_client ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling ServiceClientsApi.update_client" end # verify the required parameter 'client_id' is set - if @api_client.config.client_side_validation && client_id.nil? + if @authress_client.config.client_side_validation && client_id.nil? fail ArgumentError, "Missing the required parameter 'client_id' when calling ServiceClientsApi.update_client" end # resource path @@ -388,20 +381,20 @@ def update_client_with_http_info(body, client_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse20014' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:PUT, local_var_path, + data, status_code, headers = @authress_client.call_api(:PUT, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -409,8 +402,8 @@ def update_client_with_http_info(body, client_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: ServiceClientsApi#update_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: ServiceClientsApi#update_client\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end diff --git a/lib/swagger_client/api/user_permissions_api.rb b/lib/authress_sdk/api/user_permissions_api.rb similarity index 75% rename from lib/swagger_client/api/user_permissions_api.rb rename to lib/authress_sdk/api/user_permissions_api.rb index 6cfe214..897f130 100644 --- a/lib/swagger_client/api/user_permissions_api.rb +++ b/lib/authress_sdk/api/user_permissions_api.rb @@ -1,20 +1,13 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end -module SwaggerClient +module AuthressSdk class UserPermissionsApi - attr_accessor :api_client + attr_accessor :authress_client - def initialize(api_client = ApiClient.default) - @api_client = api_client + def initialize(authress_client = AuthressClient.default) + @authress_client = authress_client end # Check to see if a user has permissions to a resource. # Billable Does the user have the specified permissions to the resource?
READ: Authress:UserPermissions/{userId} @@ -36,19 +29,19 @@ def authorize_user(user_id, resource_uri, permission, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def authorize_user_with_http_info(user_id, resource_uri, permission, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: UserPermissionsApi.authorize_user ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: UserPermissionsApi.authorize_user ...' end # verify the required parameter 'user_id' is set - if @api_client.config.client_side_validation && user_id.nil? + if @authress_client.config.client_side_validation && user_id.nil? fail ArgumentError, "Missing the required parameter 'user_id' when calling UserPermissionsApi.authorize_user" end # verify the required parameter 'resource_uri' is set - if @api_client.config.client_side_validation && resource_uri.nil? + if @authress_client.config.client_side_validation && resource_uri.nil? fail ArgumentError, "Missing the required parameter 'resource_uri' when calling UserPermissionsApi.authorize_user" end # verify the required parameter 'permission' is set - if @api_client.config.client_side_validation && permission.nil? + if @authress_client.config.client_side_validation && permission.nil? fail ArgumentError, "Missing the required parameter 'permission' when calling UserPermissionsApi.authorize_user" end # resource path @@ -69,7 +62,7 @@ def authorize_user_with_http_info(user_id, resource_uri, permission, opts = {}) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -77,8 +70,8 @@ def authorize_user_with_http_info(user_id, resource_uri, permission, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: UserPermissionsApi#authorize_user\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: UserPermissionsApi#authorize_user\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -100,15 +93,15 @@ def disable_user_token(user_id, token_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers def disable_user_token_with_http_info(user_id, token_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: UserPermissionsApi.disable_user_token ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: UserPermissionsApi.disable_user_token ...' end # verify the required parameter 'user_id' is set - if @api_client.config.client_side_validation && user_id.nil? + if @authress_client.config.client_side_validation && user_id.nil? fail ArgumentError, "Missing the required parameter 'user_id' when calling UserPermissionsApi.disable_user_token" end # verify the required parameter 'token_id' is set - if @api_client.config.client_side_validation && token_id.nil? + if @authress_client.config.client_side_validation && token_id.nil? fail ArgumentError, "Missing the required parameter 'token_id' when calling UserPermissionsApi.disable_user_token" end # resource path @@ -129,7 +122,7 @@ def disable_user_token_with_http_info(user_id, token_id, opts = {}) return_type = opts[:return_type] auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:DELETE, local_var_path, + data, status_code, headers = @authress_client.call_api(:DELETE, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -137,8 +130,8 @@ def disable_user_token_with_http_info(user_id, token_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: UserPermissionsApi#disable_user_token\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: UserPermissionsApi#disable_user_token\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -160,15 +153,15 @@ def get_user_permissions_for_resource(user_id, resource_uri, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2002, Integer, Hash)>] InlineResponse2002 data, response status code and response headers def get_user_permissions_for_resource_with_http_info(user_id, resource_uri, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: UserPermissionsApi.get_user_permissions_for_resource ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: UserPermissionsApi.get_user_permissions_for_resource ...' end # verify the required parameter 'user_id' is set - if @api_client.config.client_side_validation && user_id.nil? + if @authress_client.config.client_side_validation && user_id.nil? fail ArgumentError, "Missing the required parameter 'user_id' when calling UserPermissionsApi.get_user_permissions_for_resource" end # verify the required parameter 'resource_uri' is set - if @api_client.config.client_side_validation && resource_uri.nil? + if @authress_client.config.client_side_validation && resource_uri.nil? fail ArgumentError, "Missing the required parameter 'resource_uri' when calling UserPermissionsApi.get_user_permissions_for_resource" end # resource path @@ -180,7 +173,7 @@ def get_user_permissions_for_resource_with_http_info(user_id, resource_uri, opts # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -191,7 +184,7 @@ def get_user_permissions_for_resource_with_http_info(user_id, resource_uri, opts return_type = opts[:return_type] || 'InlineResponse2002' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -199,8 +192,8 @@ def get_user_permissions_for_resource_with_http_info(user_id, resource_uri, opts :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: UserPermissionsApi#get_user_permissions_for_resource\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: UserPermissionsApi#get_user_permissions_for_resource\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -228,11 +221,11 @@ def get_user_resources(user_id, opts = {}) # @option opts [String] :cursor Continuation cursor for paging (will automatically be set) # @return [Array<(InlineResponse200, Integer, Hash)>] InlineResponse200 data, response status code and response headers def get_user_resources_with_http_info(user_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: UserPermissionsApi.get_user_resources ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: UserPermissionsApi.get_user_resources ...' end # verify the required parameter 'user_id' is set - if @api_client.config.client_side_validation && user_id.nil? + if @authress_client.config.client_side_validation && user_id.nil? fail ArgumentError, "Missing the required parameter 'user_id' when calling UserPermissionsApi.get_user_resources" end # resource path @@ -248,7 +241,7 @@ def get_user_resources_with_http_info(user_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # form parameters form_params = opts[:form_params] || {} @@ -259,7 +252,7 @@ def get_user_resources_with_http_info(user_id, opts = {}) return_type = opts[:return_type] || 'InlineResponse200' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:GET, local_var_path, + data, status_code, headers = @authress_client.call_api(:GET, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -267,8 +260,8 @@ def get_user_resources_with_http_info(user_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: UserPermissionsApi#get_user_resources\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: UserPermissionsApi#get_user_resources\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end @@ -290,15 +283,15 @@ def request_user_token(body, user_id, opts = {}) # @param [Hash] opts the optional parameters # @return [Array<(InlineResponse2003, Integer, Hash)>] InlineResponse2003 data, response status code and response headers def request_user_token_with_http_info(body, user_id, opts = {}) - if @api_client.config.debugging - @api_client.config.logger.debug 'Calling API: UserPermissionsApi.request_user_token ...' + if @authress_client.config.debugging + @authress_client.config.logger.debug 'Calling API: UserPermissionsApi.request_user_token ...' end # verify the required parameter 'body' is set - if @api_client.config.client_side_validation && body.nil? + if @authress_client.config.client_side_validation && body.nil? fail ArgumentError, "Missing the required parameter 'body' when calling UserPermissionsApi.request_user_token" end # verify the required parameter 'user_id' is set - if @api_client.config.client_side_validation && user_id.nil? + if @authress_client.config.client_side_validation && user_id.nil? fail ArgumentError, "Missing the required parameter 'user_id' when calling UserPermissionsApi.request_user_token" end # resource path @@ -310,20 +303,20 @@ def request_user_token_with_http_info(body, user_id, opts = {}) # header parameters header_params = opts[:header_params] || {} # HTTP header 'Accept' (if needed) - header_params['Accept'] = @api_client.select_header_accept(['application/links+json']) + header_params['Accept'] = @authress_client.select_header_accept(['application/links+json']) # HTTP header 'Content-Type' - header_params['Content-Type'] = @api_client.select_header_content_type(['application/json']) + header_params['Content-Type'] = @authress_client.select_header_content_type(['application/json']) # form parameters form_params = opts[:form_params] || {} # http body (model) - post_body = opts[:body] || @api_client.object_to_http_body(body) + post_body = opts[:body] || @authress_client.object_to_http_body(body) return_type = opts[:return_type] || 'InlineResponse2003' auth_names = opts[:auth_names] || ['oauth2'] - data, status_code, headers = @api_client.call_api(:POST, local_var_path, + data, status_code, headers = @authress_client.call_api(:POST, local_var_path, :header_params => header_params, :query_params => query_params, :form_params => form_params, @@ -331,8 +324,8 @@ def request_user_token_with_http_info(body, user_id, opts = {}) :auth_names => auth_names, :return_type => return_type) - if @api_client.config.debugging - @api_client.config.logger.debug "API called: UserPermissionsApi#request_user_token\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + if @authress_client.config.debugging + @authress_client.config.logger.debug "API called: UserPermissionsApi#request_user_token\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" end return data, status_code, headers end diff --git a/lib/authress_sdk/api_error.rb b/lib/authress_sdk/api_error.rb new file mode 100644 index 0000000..828c3d4 --- /dev/null +++ b/lib/authress_sdk/api_error.rb @@ -0,0 +1,50 @@ +=begin + +=end + +module AuthressSdk + class ApiError < StandardError + attr_reader :code, :response_headers, :response_body + + # Usage examples: + # ApiError.new + # ApiError.new("message") + # ApiError.new(:code => 500, :response_headers => {}, :response_body => "") + # ApiError.new(:code => 404, :message => "Not Found") + def initialize(arg = nil) + if arg.is_a? Hash + if arg.key?(:message) || arg.key?('message') + super(arg[:message] || arg['message']) + else + super arg + end + + arg.each do |k, v| + instance_variable_set "@#{k}", v + end + else + super arg + end + end + + # Override to_s to display a friendly error message + def to_s + message + end + + def message + if @message.nil? + msg = "Error message: the server returns an error" + else + msg = @message + end + + msg += "\nHTTP status code: #{code}" if code + msg += "\nResponse headers: #{response_headers}" if response_headers + msg += "\nResponse body: #{response_body}" if response_body + + msg + end + + end +end diff --git a/lib/swagger_client/api_client.rb b/lib/authress_sdk/authress_client.rb similarity index 57% rename from lib/swagger_client/api_client.rb rename to lib/authress_sdk/authress_client.rb index 9e256d2..01f4ffd 100644 --- a/lib/swagger_client/api_client.rb +++ b/lib/authress_sdk/authress_client.rb @@ -1,12 +1,5 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' @@ -16,29 +9,34 @@ require 'typhoeus' require 'uri' -module SwaggerClient - class ApiClient +module AuthressSdk + class AuthressClient # The Configuration object holding settings to be used in the API client. attr_accessor :config - # Defines the headers to be used in HTTP requests of all API calls by default. - # - # @return [Hash] - attr_accessor :default_headers - - # Initializes the ApiClient - # @option config [Configuration] Configuration for initializing the object, default to Configuration.default - def initialize(config = Configuration.default) - @config = config - @user_agent = "Swagger-Codegen/#{VERSION}/ruby" - @default_headers = { - 'Content-Type' => 'application/json', - 'User-Agent' => @user_agent + # The Base URL + attr_accessor :base_url + + # Token Provider + attr_accessor :token_provider + + # Initializes the AuthressClient + def initialize() + @config = { + :logger => Logger.new(STDOUT), + :debugging => false, + :client_side_validation => true } + + @token_provider = ConstantTokenProvider.new(nil) end def self.default - @@default ||= ApiClient.new + @@default ||= AuthressClient.new + end + + def set_token(token) + @token_provider = ConstantTokenProvider.new(token) end # Call an API with given options. @@ -49,10 +47,6 @@ def call_api(http_method, path, opts = {}) request = build_request(http_method, path, opts) response = request.run - if @config.debugging - @config.logger.debug "HTTP response body ~BEGIN~\n#{response.body}\n~END~\n" - end - unless response.success? if response.timed_out? fail ApiError.new('Connection timed out') @@ -89,41 +83,36 @@ def build_request(http_method, path, opts = {}) url = build_request_url(path) http_method = http_method.to_sym.downcase - header_params = @default_headers.merge(opts[:header_params] || {}) + default_headers = { + 'Content-Type' => 'application/json', + 'User-Agent' => "Ruby AuthressSDK version: #{Gem.loaded_specs["authress-sdk"].version.to_s}" + } + header_params = default_headers.merge(opts[:header_params] || {}) query_params = opts[:query_params] || {} form_params = opts[:form_params] || {} - update_params_for_auth! header_params, query_params, opts[:auth_names] + if !@token_provider.nil? + header_params['Authorization'] = "Bearer #{@token_provider.get_token()}" + end # set ssl_verifyhosts option based on @config.verify_ssl_host (true/false) - _verify_ssl_host = @config.verify_ssl_host ? 2 : 0 + _verify_ssl_host = 2 req_opts = { :method => http_method, :headers => header_params, :params => query_params, - :params_encoding => @config.params_encoding, - :timeout => @config.timeout, - :ssl_verifypeer => @config.verify_ssl, - :ssl_verifyhost => _verify_ssl_host, - :sslcert => @config.cert_file, - :sslkey => @config.key_file, - :verbose => @config.debugging + :ssl_verifypeer => true, + :ssl_verifyhost => true, + :verbose => false } - # set custom cert, if provided - req_opts[:cainfo] = @config.ssl_ca_cert if @config.ssl_ca_cert - - if [:post, :patch, :put, :delete].include?(http_method) + if [:post, :patch, :put].include?(http_method) req_body = build_request_body(header_params, form_params, opts[:body]) req_opts.update :body => req_body - if @config.debugging - @config.logger.debug "HTTP request body param ~BEGIN~\n#{req_body}\n~END~\n" - end end request = Typhoeus::Request.new(url, req_opts) - download_file(request) if opts[:return_type] == 'File' request end @@ -237,45 +226,7 @@ def convert_to_type(data, return_type) end else # models, e.g. Pet - SwaggerClient.const_get(return_type).build_from_hash(data) - end - end - - # Save response body into a file in (the defined) temporary folder, using the filename - # from the "Content-Disposition" header if provided, otherwise a random filename. - # The response body is written to the file in chunks in order to handle files which - # size is larger than maximum Ruby String or even larger than the maximum memory a Ruby - # process can use. - # - # @see Configuration#temp_folder_path - def download_file(request) - tempfile = nil - encoding = nil - request.on_headers do |response| - content_disposition = response.headers['Content-Disposition'] - if content_disposition && content_disposition =~ /filename=/i - filename = content_disposition[/filename=['"]?([^'"\s]+)['"]?/, 1] - prefix = sanitize_filename(filename) - else - prefix = 'download-' - end - prefix = prefix + '-' unless prefix.end_with?('-') - encoding = response.body.encoding - tempfile = Tempfile.open(prefix, @config.temp_folder_path, encoding: encoding) - @tempfile = tempfile - end - request.on_body do |chunk| - chunk.force_encoding(encoding) - tempfile.write(chunk) - end - request.on_complete do |response| - if tempfile - tempfile.close - @config.logger.info "Temp file written to #{tempfile.path}, please copy the file to a proper folder "\ - "with e.g. `FileUtils.cp(tempfile.path, '/new/file/path')` otherwise the temp file "\ - "will be deleted automatically with GC. It's also recommended to delete the temp file "\ - "explicitly with `tempfile.delete`" - end + AuthressSdk.const_get(return_type).build_from_hash(data) end end @@ -291,32 +242,7 @@ def sanitize_filename(filename) def build_request_url(path) # Add leading and trailing slashes to path path = "/#{path}".gsub(/\/+/, '/') - @config.base_url + path - end - - # Update hearder and query params based on authentication settings. - # - # @param [Hash] header_params Header parameters - # @param [Hash] query_params Query parameters - # @param [String] auth_names Authentication scheme name - def update_params_for_auth!(header_params, query_params, auth_names) - Array(auth_names).each do |auth_name| - auth_setting = @config.auth_settings[auth_name] - next unless auth_setting - case auth_setting[:in] - when 'header' then header_params[auth_setting[:key]] = auth_setting[:value] - when 'query' then query_params[auth_setting[:key]] = auth_setting[:value] - else fail ArgumentError, 'Authentication token must be in `query` of `header`' - end - end - end - - # Sets user agent in HTTP header - # - # @param [String] user_agent User agent (e.g. swagger-codegen/ruby/1.0.0) - def user_agent=(user_agent) - @user_agent = user_agent - @default_headers['User-Agent'] = @user_agent + @base_url + path end # Return Accept header based on an array of accepts provided. diff --git a/lib/authress_sdk/constant_token_provider.rb b/lib/authress_sdk/constant_token_provider.rb new file mode 100644 index 0000000..cbf60d9 --- /dev/null +++ b/lib/authress_sdk/constant_token_provider.rb @@ -0,0 +1,19 @@ +require 'date' +require 'json' +require 'logger' +require 'tempfile' +require 'typhoeus' +require 'uri' + +module AuthressSdk + class ConstantTokenProvider + + def initialize(access_token) + @access_token = access_token + end + + def get_token + @access_token + end + end +end diff --git a/lib/swagger_client/models/access_record.rb b/lib/authress_sdk/models/access_record.rb similarity index 79% rename from lib/swagger_client/models/access_record.rb rename to lib/authress_sdk/models/access_record.rb index 5e225c0..c679585 100644 --- a/lib/swagger_client/models/access_record.rb +++ b/lib/authress_sdk/models/access_record.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The access record which links users to roles. class AccessRecord # Unique identifier for the record, can be specified on record creation. @@ -101,13 +94,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::AccessRecord` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::AccessRecord` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::AccessRecord`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::AccessRecord`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -299,7 +292,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/access_record_collection.rb b/lib/authress_sdk/models/access_record_collection.rb similarity index 70% rename from lib/swagger_client/models/access_record_collection.rb rename to lib/authress_sdk/models/access_record_collection.rb index 26f1a39..a895562 100644 --- a/lib/swagger_client/models/access_record_collection.rb +++ b/lib/authress_sdk/models/access_record_collection.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collection of access records class AccessRecordCollection # A list of access records @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::AccessRecordCollection` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::AccessRecordCollection` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::AccessRecordCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::AccessRecordCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/access_record_collection_records.rb b/lib/authress_sdk/models/access_record_collection_records.rb similarity index 79% rename from lib/swagger_client/models/access_record_collection_records.rb rename to lib/authress_sdk/models/access_record_collection_records.rb index c6fe8f1..42a60cb 100644 --- a/lib/swagger_client/models/access_record_collection_records.rb +++ b/lib/authress_sdk/models/access_record_collection_records.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The access record which links users to roles. class AccessRecordCollectionRecords # Unique identifier for the record, can be specified on record creation. @@ -101,13 +94,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::AccessRecordCollectionRecords` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::AccessRecordCollectionRecords` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::AccessRecordCollectionRecords`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::AccessRecordCollectionRecords`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -299,7 +292,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/account.rb b/lib/authress_sdk/models/account.rb similarity index 74% rename from lib/swagger_client/models/account.rb rename to lib/authress_sdk/models/account.rb index cdfbee5..7017baf 100644 --- a/lib/swagger_client/models/account.rb +++ b/lib/authress_sdk/models/account.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class Account attr_accessor :account_id @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Account` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Account` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Account`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Account`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -216,7 +209,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_11.rb b/lib/authress_sdk/models/account_collection.rb similarity index 69% rename from lib/swagger_client/models/inline_response_200_11.rb rename to lib/authress_sdk/models/account_collection.rb index 6858304..a1e4205 100644 --- a/lib/swagger_client/models/inline_response_200_11.rb +++ b/lib/authress_sdk/models/account_collection.rb @@ -1,18 +1,11 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient - class InlineResponse20011 +module AuthressSdk + class AccountCollection attr_accessor :accounts # Attribute mapping from ruby-style variable name to JSON key. @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse20011` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::AccountCollection` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse20011`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::AccountCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -159,7 +152,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/account_collection_accounts.rb b/lib/authress_sdk/models/account_collection_accounts.rb similarity index 74% rename from lib/swagger_client/models/account_collection_accounts.rb rename to lib/authress_sdk/models/account_collection_accounts.rb index e5e6a96..01f1725 100644 --- a/lib/swagger_client/models/account_collection_accounts.rb +++ b/lib/authress_sdk/models/account_collection_accounts.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class AccountCollectionAccounts attr_accessor :account_id @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::AccountCollectionAccounts` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::AccountCollectionAccounts` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::AccountCollectionAccounts`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::AccountCollectionAccounts`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -216,7 +209,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body.rb b/lib/authress_sdk/models/body.rb similarity index 72% rename from lib/swagger_client/models/body.rb rename to lib/authress_sdk/models/body.rb index a18d88c..918f497 100644 --- a/lib/swagger_client/models/body.rb +++ b/lib/authress_sdk/models/body.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # Metadata and additional properties relevant. class Body attr_accessor :account @@ -49,13 +42,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -184,7 +177,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_1.rb b/lib/authress_sdk/models/body_1.rb similarity index 71% rename from lib/swagger_client/models/body_1.rb rename to lib/authress_sdk/models/body_1.rb index 7134509..d3b581c 100644 --- a/lib/swagger_client/models/body_1.rb +++ b/lib/authress_sdk/models/body_1.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class Body1 # A list of statements which match roles to resources. The token will have all statements apply to it. attr_accessor :statements @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body1` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body1` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body1`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body1`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_10.rb b/lib/authress_sdk/models/body_10.rb similarity index 72% rename from lib/swagger_client/models/body_10.rb rename to lib/authress_sdk/models/body_10.rb index 6541059..de44016 100644 --- a/lib/swagger_client/models/body_10.rb +++ b/lib/authress_sdk/models/body_10.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A client configuration. class Body10 # The unique id of the client. @@ -54,13 +47,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body10` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body10` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body10`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body10`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -194,7 +187,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_11.rb b/lib/authress_sdk/models/body_11.rb similarity index 72% rename from lib/swagger_client/models/body_11.rb rename to lib/authress_sdk/models/body_11.rb index cd7775d..b8b2a2f 100644 --- a/lib/swagger_client/models/body_11.rb +++ b/lib/authress_sdk/models/body_11.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A client configuration. class Body11 # The unique id of the client. @@ -54,13 +47,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body11` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body11` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body11`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body11`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -194,7 +187,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_2.rb b/lib/authress_sdk/models/body_2.rb similarity index 69% rename from lib/swagger_client/models/body_2.rb rename to lib/authress_sdk/models/body_2.rb index af38f58..af24db8 100644 --- a/lib/swagger_client/models/body_2.rb +++ b/lib/authress_sdk/models/body_2.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class Body2 attr_accessor :permissions @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body2` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body2` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body2`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body2`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -161,7 +154,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_3.rb b/lib/authress_sdk/models/body_3.rb similarity index 79% rename from lib/swagger_client/models/body_3.rb rename to lib/authress_sdk/models/body_3.rb index bdfe253..897d1bc 100644 --- a/lib/swagger_client/models/body_3.rb +++ b/lib/authress_sdk/models/body_3.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The access record which links users to roles. class Body3 # Unique identifier for the record, can be specified on record creation. @@ -101,13 +94,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body3` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body3` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body3`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body3`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -299,7 +292,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_4.rb b/lib/authress_sdk/models/body_4.rb similarity index 79% rename from lib/swagger_client/models/body_4.rb rename to lib/authress_sdk/models/body_4.rb index 979ee54..320f6b7 100644 --- a/lib/swagger_client/models/body_4.rb +++ b/lib/authress_sdk/models/body_4.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The access record which links users to roles. class Body4 # Unique identifier for the record, can be specified on record creation. @@ -101,13 +94,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body4` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body4` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body4`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body4`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -299,7 +292,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_5.rb b/lib/authress_sdk/models/body_5.rb similarity index 71% rename from lib/swagger_client/models/body_5.rb rename to lib/authress_sdk/models/body_5.rb index b5679c2..1d677d8 100644 --- a/lib/swagger_client/models/body_5.rb +++ b/lib/authress_sdk/models/body_5.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The user invite used to invite users to your application. class Body5 # Only used when the invite includes Authress specific permissions. If no Authress permissions are defined in the statements, then the email will not be used. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body5` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body5` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body5`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body5`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -173,7 +166,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_6.rb b/lib/authress_sdk/models/body_6.rb similarity index 73% rename from lib/swagger_client/models/body_6.rb rename to lib/authress_sdk/models/body_6.rb index 7029e77..7af5612 100644 --- a/lib/swagger_client/models/body_6.rb +++ b/lib/authress_sdk/models/body_6.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The role which contains a list of permissions. class Body6 # Unique identifier for the role, can be specified on creation, and used by records to map to permissions. @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body6` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body6` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body6`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body6`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -203,7 +196,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_7.rb b/lib/authress_sdk/models/body_7.rb similarity index 73% rename from lib/swagger_client/models/body_7.rb rename to lib/authress_sdk/models/body_7.rb index bdecf92..3f19eef 100644 --- a/lib/swagger_client/models/body_7.rb +++ b/lib/authress_sdk/models/body_7.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The role which contains a list of permissions. class Body7 # Unique identifier for the role, can be specified on creation, and used by records to map to permissions. @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body7` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body7` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body7`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body7`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -203,7 +196,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_8.rb b/lib/authress_sdk/models/body_8.rb similarity index 72% rename from lib/swagger_client/models/body_8.rb rename to lib/authress_sdk/models/body_8.rb index ff01be8..23a82c8 100644 --- a/lib/swagger_client/models/body_8.rb +++ b/lib/authress_sdk/models/body_8.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class Body8 # The parent resource to add a sub-resource to. The resource must have a resource configuration that add the permission CLAIM for this to work. attr_accessor :collection_resource @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body8` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body8` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body8`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body8`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -175,7 +168,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/body_9.rb b/lib/authress_sdk/models/body_9.rb similarity index 71% rename from lib/swagger_client/models/body_9.rb rename to lib/authress_sdk/models/body_9.rb index 5c60aac..1c5fea3 100644 --- a/lib/swagger_client/models/body_9.rb +++ b/lib/authress_sdk/models/body_9.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # Request to link an identity provider's audience and your app's audience with Authress. class Body9 # A valid JWT OIDC compliant token which will still pass authentication requests to the identity provider. Must contain a unique audience and issuer. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Body9` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Body9` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Body9`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Body9`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -171,7 +164,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/claim_request.rb b/lib/authress_sdk/models/claim_request.rb similarity index 72% rename from lib/swagger_client/models/claim_request.rb rename to lib/authress_sdk/models/claim_request.rb index 7882068..04f8c31 100644 --- a/lib/swagger_client/models/claim_request.rb +++ b/lib/authress_sdk/models/claim_request.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class ClaimRequest # The parent resource to add a sub-resource to. The resource must have a resource configuration that add the permission CLAIM for this to work. attr_accessor :collection_resource @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ClaimRequest` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ClaimRequest` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ClaimRequest`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ClaimRequest`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -175,7 +168,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/claim_response.rb b/lib/authress_sdk/models/claim_response.rb similarity index 67% rename from lib/swagger_client/models/claim_response.rb rename to lib/authress_sdk/models/claim_response.rb index df57ab5..13af96b 100644 --- a/lib/swagger_client/models/claim_response.rb +++ b/lib/authress_sdk/models/claim_response.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class ClaimResponse # Attribute mapping from ruby-style variable name to JSON key. def self.attribute_map @@ -35,13 +28,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ClaimResponse` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ClaimResponse` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ClaimResponse`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ClaimResponse`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -145,7 +138,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/client.rb b/lib/authress_sdk/models/client.rb similarity index 72% rename from lib/swagger_client/models/client.rb rename to lib/authress_sdk/models/client.rb index d459c94..45f942f 100644 --- a/lib/swagger_client/models/client.rb +++ b/lib/authress_sdk/models/client.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A client configuration. class Client # The unique id of the client. @@ -54,13 +47,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Client` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Client` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Client`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Client`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -194,7 +187,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/client_access_key.rb b/lib/authress_sdk/models/client_access_key.rb similarity index 73% rename from lib/swagger_client/models/client_access_key.rb rename to lib/authress_sdk/models/client_access_key.rb index 03fa10d..3f2dc87 100644 --- a/lib/swagger_client/models/client_access_key.rb +++ b/lib/authress_sdk/models/client_access_key.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A client configuration. class ClientAccessKey # The unique id of the client. @@ -55,13 +48,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ClientAccessKey` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ClientAccessKey` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ClientAccessKey`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ClientAccessKey`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -190,7 +183,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/client_collection.rb b/lib/authress_sdk/models/client_collection.rb similarity index 70% rename from lib/swagger_client/models/client_collection.rb rename to lib/authress_sdk/models/client_collection.rb index 5ba884a..f6f664f 100644 --- a/lib/swagger_client/models/client_collection.rb +++ b/lib/authress_sdk/models/client_collection.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The collection of a list of clients class ClientCollection # A list of clients @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ClientCollection` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ClientCollection` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ClientCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ClientCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/client_collection_clients.rb b/lib/authress_sdk/models/client_collection_clients.rb similarity index 72% rename from lib/swagger_client/models/client_collection_clients.rb rename to lib/authress_sdk/models/client_collection_clients.rb index 3677031..806c810 100644 --- a/lib/swagger_client/models/client_collection_clients.rb +++ b/lib/authress_sdk/models/client_collection_clients.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A client configuration. class ClientCollectionClients # The unique id of the client. @@ -54,13 +47,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ClientCollectionClients` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ClientCollectionClients` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ClientCollectionClients`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ClientCollectionClients`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -194,7 +187,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/identity.rb b/lib/authress_sdk/models/identity.rb similarity index 71% rename from lib/swagger_client/models/identity.rb rename to lib/authress_sdk/models/identity.rb index 9f3e633..f1f0d02 100644 --- a/lib/swagger_client/models/identity.rb +++ b/lib/authress_sdk/models/identity.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The identifying information which uniquely links a JWT OIDC token to an identity provider class Identity # The issuer of the JWT token. This can be any OIDC compliant provider. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Identity` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Identity` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Identity`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Identity`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -176,7 +169,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/identity_collection.rb b/lib/authress_sdk/models/identity_collection.rb similarity index 69% rename from lib/swagger_client/models/identity_collection.rb rename to lib/authress_sdk/models/identity_collection.rb index c34aedf..0aee0f6 100644 --- a/lib/swagger_client/models/identity_collection.rb +++ b/lib/authress_sdk/models/identity_collection.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class IdentityCollection attr_accessor :identities @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::IdentityCollection` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::IdentityCollection` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::IdentityCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::IdentityCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -161,7 +154,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/identity_collection_identities.rb b/lib/authress_sdk/models/identity_collection_identities.rb similarity index 71% rename from lib/swagger_client/models/identity_collection_identities.rb rename to lib/authress_sdk/models/identity_collection_identities.rb index 62ec947..0083c4a 100644 --- a/lib/swagger_client/models/identity_collection_identities.rb +++ b/lib/authress_sdk/models/identity_collection_identities.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The identifying information which uniquely links a JWT OIDC token to an identity provider class IdentityCollectionIdentities # The issuer of the JWT token. This can be any OIDC compliant provider. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::IdentityCollectionIdentities` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::IdentityCollectionIdentities` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::IdentityCollectionIdentities`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::IdentityCollectionIdentities`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -176,7 +169,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/identity_request.rb b/lib/authress_sdk/models/identity_request.rb similarity index 71% rename from lib/swagger_client/models/identity_request.rb rename to lib/authress_sdk/models/identity_request.rb index 6ddee8b..037d247 100644 --- a/lib/swagger_client/models/identity_request.rb +++ b/lib/authress_sdk/models/identity_request.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # Request to link an identity provider's audience and your app's audience with Authress. class IdentityRequest # A valid JWT OIDC compliant token which will still pass authentication requests to the identity provider. Must contain a unique audience and issuer. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::IdentityRequest` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::IdentityRequest` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::IdentityRequest`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::IdentityRequest`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -171,7 +164,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200.rb b/lib/authress_sdk/models/inline_response_200.rb similarity index 72% rename from lib/swagger_client/models/inline_response_200.rb rename to lib/authress_sdk/models/inline_response_200.rb index 9440967..cb377c0 100644 --- a/lib/swagger_client/models/inline_response_200.rb +++ b/lib/authress_sdk/models/inline_response_200.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collect of permissions that the user has to a resource. class InlineResponse200 attr_accessor :account @@ -53,13 +46,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse200` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse200` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse200`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse200`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -195,7 +188,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_1.rb b/lib/authress_sdk/models/inline_response_200_1.rb similarity index 72% rename from lib/swagger_client/models/inline_response_200_1.rb rename to lib/authress_sdk/models/inline_response_200_1.rb index d7b400a..37192a1 100644 --- a/lib/swagger_client/models/inline_response_200_1.rb +++ b/lib/authress_sdk/models/inline_response_200_1.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # Metadata and additional properties relevant. class InlineResponse2001 attr_accessor :account @@ -49,13 +42,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2001` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2001` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2001`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2001`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -184,7 +177,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_10.rb b/lib/authress_sdk/models/inline_response_200_10.rb similarity index 73% rename from lib/swagger_client/models/inline_response_200_10.rb rename to lib/authress_sdk/models/inline_response_200_10.rb index b8afc0c..06d42b4 100644 --- a/lib/swagger_client/models/inline_response_200_10.rb +++ b/lib/authress_sdk/models/inline_response_200_10.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The role which contains a list of permissions. class InlineResponse20010 # Unique identifier for the role, can be specified on creation, and used by records to map to permissions. @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse20010` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse20010` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse20010`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse20010`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -203,7 +196,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/account_collection.rb b/lib/authress_sdk/models/inline_response_200_11.rb similarity index 70% rename from lib/swagger_client/models/account_collection.rb rename to lib/authress_sdk/models/inline_response_200_11.rb index ede52e4..e4c2c7e 100644 --- a/lib/swagger_client/models/account_collection.rb +++ b/lib/authress_sdk/models/inline_response_200_11.rb @@ -1,18 +1,11 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient - class AccountCollection +module AuthressSdk + class InlineResponse20011 attr_accessor :accounts # Attribute mapping from ruby-style variable name to JSON key. @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::AccountCollection` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse20011` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::AccountCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse20011`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -159,7 +152,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_12.rb b/lib/authress_sdk/models/inline_response_200_12.rb similarity index 69% rename from lib/swagger_client/models/inline_response_200_12.rb rename to lib/authress_sdk/models/inline_response_200_12.rb index 75343b9..cb16d95 100644 --- a/lib/swagger_client/models/inline_response_200_12.rb +++ b/lib/authress_sdk/models/inline_response_200_12.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class InlineResponse20012 attr_accessor :identities @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse20012` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse20012` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse20012`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse20012`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -161,7 +154,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_13.rb b/lib/authress_sdk/models/inline_response_200_13.rb similarity index 70% rename from lib/swagger_client/models/inline_response_200_13.rb rename to lib/authress_sdk/models/inline_response_200_13.rb index 9c0fd42..d264bd2 100644 --- a/lib/swagger_client/models/inline_response_200_13.rb +++ b/lib/authress_sdk/models/inline_response_200_13.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The collection of a list of clients class InlineResponse20013 # A list of clients @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse20013` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse20013` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse20013`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse20013`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_14.rb b/lib/authress_sdk/models/inline_response_200_14.rb similarity index 72% rename from lib/swagger_client/models/inline_response_200_14.rb rename to lib/authress_sdk/models/inline_response_200_14.rb index ce06ba8..af44574 100644 --- a/lib/swagger_client/models/inline_response_200_14.rb +++ b/lib/authress_sdk/models/inline_response_200_14.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A client configuration. class InlineResponse20014 # The unique id of the client. @@ -54,13 +47,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse20014` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse20014` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse20014`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse20014`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -194,7 +187,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_15.rb b/lib/authress_sdk/models/inline_response_200_15.rb similarity index 73% rename from lib/swagger_client/models/inline_response_200_15.rb rename to lib/authress_sdk/models/inline_response_200_15.rb index 4e5ca53..a6ac06e 100644 --- a/lib/swagger_client/models/inline_response_200_15.rb +++ b/lib/authress_sdk/models/inline_response_200_15.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A client configuration. class InlineResponse20015 # The unique id of the client. @@ -55,13 +48,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse20015` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse20015` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse20015`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse20015`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -190,7 +183,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_2.rb b/lib/authress_sdk/models/inline_response_200_2.rb similarity index 72% rename from lib/swagger_client/models/inline_response_200_2.rb rename to lib/authress_sdk/models/inline_response_200_2.rb index 556834c..285418f 100644 --- a/lib/swagger_client/models/inline_response_200_2.rb +++ b/lib/authress_sdk/models/inline_response_200_2.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collect of permissions that the user has to a resource. class InlineResponse2002 attr_accessor :account @@ -49,13 +42,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2002` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2002` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2002`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2002`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -186,7 +179,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_3.rb b/lib/authress_sdk/models/inline_response_200_3.rb similarity index 73% rename from lib/swagger_client/models/inline_response_200_3.rb rename to lib/authress_sdk/models/inline_response_200_3.rb index 67877ff..b02b3bd 100644 --- a/lib/swagger_client/models/inline_response_200_3.rb +++ b/lib/authress_sdk/models/inline_response_200_3.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A JWT token with represents the user. class InlineResponse2003 attr_accessor :account @@ -58,13 +51,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2003` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2003` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2003`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2003`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -208,7 +201,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_4.rb b/lib/authress_sdk/models/inline_response_200_4.rb similarity index 71% rename from lib/swagger_client/models/inline_response_200_4.rb rename to lib/authress_sdk/models/inline_response_200_4.rb index 726cc69..27f8417 100644 --- a/lib/swagger_client/models/inline_response_200_4.rb +++ b/lib/authress_sdk/models/inline_response_200_4.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collection of resource permissions that have been defined. class InlineResponse2004 attr_accessor :resources @@ -44,13 +37,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2004` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2004` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2004`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2004`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -176,7 +169,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_5.rb b/lib/authress_sdk/models/inline_response_200_5.rb similarity index 69% rename from lib/swagger_client/models/inline_response_200_5.rb rename to lib/authress_sdk/models/inline_response_200_5.rb index 917ee3d..cdfe98d 100644 --- a/lib/swagger_client/models/inline_response_200_5.rb +++ b/lib/authress_sdk/models/inline_response_200_5.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class InlineResponse2005 attr_accessor :permissions @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2005` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2005` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2005`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2005`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -161,7 +154,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_6.rb b/lib/authress_sdk/models/inline_response_200_6.rb similarity index 70% rename from lib/swagger_client/models/inline_response_200_6.rb rename to lib/authress_sdk/models/inline_response_200_6.rb index dda6884..1faecc1 100644 --- a/lib/swagger_client/models/inline_response_200_6.rb +++ b/lib/authress_sdk/models/inline_response_200_6.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collection of users with explicit permission to a resource. class InlineResponse2006 # A list of users @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2006` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2006` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2006`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2006`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_7.rb b/lib/authress_sdk/models/inline_response_200_7.rb similarity index 70% rename from lib/swagger_client/models/inline_response_200_7.rb rename to lib/authress_sdk/models/inline_response_200_7.rb index c9e2dcc..972f98f 100644 --- a/lib/swagger_client/models/inline_response_200_7.rb +++ b/lib/authress_sdk/models/inline_response_200_7.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collection of access records class InlineResponse2007 # A list of access records @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2007` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2007` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2007`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2007`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_8.rb b/lib/authress_sdk/models/inline_response_200_8.rb similarity index 79% rename from lib/swagger_client/models/inline_response_200_8.rb rename to lib/authress_sdk/models/inline_response_200_8.rb index 08e9cb7..4426dfd 100644 --- a/lib/swagger_client/models/inline_response_200_8.rb +++ b/lib/authress_sdk/models/inline_response_200_8.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The access record which links users to roles. class InlineResponse2008 # Unique identifier for the record, can be specified on record creation. @@ -101,13 +94,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2008` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2008` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2008`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2008`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -299,7 +292,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/inline_response_200_9.rb b/lib/authress_sdk/models/inline_response_200_9.rb similarity index 74% rename from lib/swagger_client/models/inline_response_200_9.rb rename to lib/authress_sdk/models/inline_response_200_9.rb index 236c9c2..0e86cbd 100644 --- a/lib/swagger_client/models/inline_response_200_9.rb +++ b/lib/authress_sdk/models/inline_response_200_9.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class InlineResponse2009 attr_accessor :account_id @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::InlineResponse2009` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::InlineResponse2009` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::InlineResponse2009`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::InlineResponse2009`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -216,7 +209,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/invite.rb b/lib/authress_sdk/models/invite.rb similarity index 71% rename from lib/swagger_client/models/invite.rb rename to lib/authress_sdk/models/invite.rb index 67bc89f..b20a931 100644 --- a/lib/swagger_client/models/invite.rb +++ b/lib/authress_sdk/models/invite.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The user invite used to invite users to your application. class Invite # Only used when the invite includes Authress specific permissions. If no Authress permissions are defined in the statements, then the email will not be used. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Invite` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Invite` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Invite`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Invite`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -173,7 +166,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/link.rb b/lib/authress_sdk/models/link.rb similarity index 71% rename from lib/swagger_client/models/link.rb rename to lib/authress_sdk/models/link.rb index ab8d9d2..c251417 100644 --- a/lib/swagger_client/models/link.rb +++ b/lib/authress_sdk/models/link.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A url linking object that complies to application/links+json RFC. Either is an IANA approved link relation or has a custom rel specified. class Link # The absolute url pointing to the reference resource. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Link` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Link` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Link`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Link`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -171,7 +164,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/metadata_object.rb b/lib/authress_sdk/models/metadata_object.rb similarity index 72% rename from lib/swagger_client/models/metadata_object.rb rename to lib/authress_sdk/models/metadata_object.rb index be80782..08b5667 100644 --- a/lib/swagger_client/models/metadata_object.rb +++ b/lib/authress_sdk/models/metadata_object.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # Metadata and additional properties relevant. class MetadataObject attr_accessor :account @@ -49,13 +42,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::MetadataObject` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::MetadataObject` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::MetadataObject`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::MetadataObject`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -184,7 +177,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1roles_permissions.rb b/lib/authress_sdk/models/permission_object.rb similarity index 74% rename from lib/swagger_client/models/v1roles_permissions.rb rename to lib/authress_sdk/models/permission_object.rb index 808d534..3bb3fe1 100644 --- a/lib/swagger_client/models/v1roles_permissions.rb +++ b/lib/authress_sdk/models/permission_object.rb @@ -1,19 +1,12 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The collective action and associate grants on a permission - class V1rolesPermissions + class PermissionObject # The action the permission grants, can be scoped using `:` and parent actions imply sub-resource permissions, action:* or action implies action:sub-action. This property is case-insensitive, it will always be cast to lowercase before comparing actions to user permissions. attr_accessor :action @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1rolesPermissions` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::PermissionObject` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1rolesPermissions`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::PermissionObject`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -206,7 +199,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/permission_response.rb b/lib/authress_sdk/models/permission_response.rb similarity index 72% rename from lib/swagger_client/models/permission_response.rb rename to lib/authress_sdk/models/permission_response.rb index dd9fa66..de2bcdd 100644 --- a/lib/swagger_client/models/permission_response.rb +++ b/lib/authress_sdk/models/permission_response.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collect of permissions that the user has to a resource. class PermissionResponse attr_accessor :account @@ -49,13 +42,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::PermissionResponse` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::PermissionResponse` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::PermissionResponse`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::PermissionResponse`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -186,7 +179,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/resource_permission.rb b/lib/authress_sdk/models/resource_permission.rb similarity index 69% rename from lib/swagger_client/models/resource_permission.rb rename to lib/authress_sdk/models/resource_permission.rb index 005836a..a72bbf9 100644 --- a/lib/swagger_client/models/resource_permission.rb +++ b/lib/authress_sdk/models/resource_permission.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class ResourcePermission attr_accessor :permissions @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ResourcePermission` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ResourcePermission` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ResourcePermission`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ResourcePermission`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -161,7 +154,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/resource_permission_collection.rb b/lib/authress_sdk/models/resource_permission_collection.rb similarity index 70% rename from lib/swagger_client/models/resource_permission_collection.rb rename to lib/authress_sdk/models/resource_permission_collection.rb index fe86966..2b7357c 100644 --- a/lib/swagger_client/models/resource_permission_collection.rb +++ b/lib/authress_sdk/models/resource_permission_collection.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collection of resource permissions that have been defined. class ResourcePermissionCollection attr_accessor :resources @@ -44,13 +37,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ResourcePermissionCollection` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ResourcePermissionCollection` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ResourcePermissionCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ResourcePermissionCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -176,7 +169,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/resource_permission_collection_links.rb b/lib/authress_sdk/models/resource_permission_collection_links.rb similarity index 69% rename from lib/swagger_client/models/resource_permission_collection_links.rb rename to lib/authress_sdk/models/resource_permission_collection_links.rb index b8fc42d..177ef1c 100644 --- a/lib/swagger_client/models/resource_permission_collection_links.rb +++ b/lib/authress_sdk/models/resource_permission_collection_links.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class ResourcePermissionCollectionLinks attr_accessor :_self @@ -43,13 +36,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ResourcePermissionCollectionLinks` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ResourcePermissionCollectionLinks` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ResourcePermissionCollectionLinks`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ResourcePermissionCollectionLinks`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -168,7 +161,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/resource_permission_collection_links_next.rb b/lib/authress_sdk/models/resource_permission_collection_links_next.rb similarity index 70% rename from lib/swagger_client/models/resource_permission_collection_links_next.rb rename to lib/authress_sdk/models/resource_permission_collection_links_next.rb index 1edcfcb..1ebac57 100644 --- a/lib/swagger_client/models/resource_permission_collection_links_next.rb +++ b/lib/authress_sdk/models/resource_permission_collection_links_next.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A link pointing to the next page in the collection if it exists. If there is no next page this property will not exist. class ResourcePermissionCollectionLinksNext # The absolute url pointing to the reference resource. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ResourcePermissionCollectionLinksNext` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ResourcePermissionCollectionLinksNext` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ResourcePermissionCollectionLinksNext`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ResourcePermissionCollectionLinksNext`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -171,7 +164,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/resource_permission_collection_resources.rb b/lib/authress_sdk/models/resource_permission_collection_resources.rb similarity index 69% rename from lib/swagger_client/models/resource_permission_collection_resources.rb rename to lib/authress_sdk/models/resource_permission_collection_resources.rb index adcc28f..9806425 100644 --- a/lib/swagger_client/models/resource_permission_collection_resources.rb +++ b/lib/authress_sdk/models/resource_permission_collection_resources.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class ResourcePermissionCollectionResources attr_accessor :permissions @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ResourcePermissionCollectionResources` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ResourcePermissionCollectionResources` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ResourcePermissionCollectionResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ResourcePermissionCollectionResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -161,7 +154,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/resource_users_collection.rb b/lib/authress_sdk/models/resource_users_collection.rb similarity index 70% rename from lib/swagger_client/models/resource_users_collection.rb rename to lib/authress_sdk/models/resource_users_collection.rb index d6f75c2..c7a922c 100644 --- a/lib/swagger_client/models/resource_users_collection.rb +++ b/lib/authress_sdk/models/resource_users_collection.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collection of users with explicit permission to a resource. class ResourceUsersCollection # A list of users @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::ResourceUsersCollection` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::ResourceUsersCollection` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::ResourceUsersCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::ResourceUsersCollection`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/role.rb b/lib/authress_sdk/models/role.rb similarity index 73% rename from lib/swagger_client/models/role.rb rename to lib/authress_sdk/models/role.rb index 4956f95..cf55dfd 100644 --- a/lib/swagger_client/models/role.rb +++ b/lib/authress_sdk/models/role.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The role which contains a list of permissions. class Role # Unique identifier for the role, can be specified on creation, and used by records to map to permissions. @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Role` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Role` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Role`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Role`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -203,7 +196,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/statement.rb b/lib/authress_sdk/models/statement.rb similarity index 71% rename from lib/swagger_client/models/statement.rb rename to lib/authress_sdk/models/statement.rb index 55f78b0..cf21a7a 100644 --- a/lib/swagger_client/models/statement.rb +++ b/lib/authress_sdk/models/statement.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class Statement attr_accessor :roles @@ -43,13 +36,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::Statement` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::Statement` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::Statement`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::Statement`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/token_request.rb b/lib/authress_sdk/models/token_request.rb similarity index 71% rename from lib/swagger_client/models/token_request.rb rename to lib/authress_sdk/models/token_request.rb index 4ecf1b5..b71793c 100644 --- a/lib/swagger_client/models/token_request.rb +++ b/lib/authress_sdk/models/token_request.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class TokenRequest # A list of statements which match roles to resources. The token will have all statements apply to it. attr_accessor :statements @@ -45,13 +38,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::TokenRequest` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::TokenRequest` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::TokenRequest`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::TokenRequest`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/user.rb b/lib/authress_sdk/models/user.rb similarity index 69% rename from lib/swagger_client/models/user.rb rename to lib/authress_sdk/models/user.rb index 94514c4..e48d000 100644 --- a/lib/swagger_client/models/user.rb +++ b/lib/authress_sdk/models/user.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A user object that identifies a user. class User attr_accessor :user_id @@ -40,13 +33,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::User` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::User` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::User`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::User`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -160,7 +153,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/user_resources.rb b/lib/authress_sdk/models/user_resources.rb similarity index 72% rename from lib/swagger_client/models/user_resources.rb rename to lib/authress_sdk/models/user_resources.rb index f88cb4d..b454efe 100644 --- a/lib/swagger_client/models/user_resources.rb +++ b/lib/authress_sdk/models/user_resources.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A collect of permissions that the user has to a resource. class UserResources attr_accessor :account @@ -53,13 +46,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::UserResources` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::UserResources` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::UserResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::UserResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -195,7 +188,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/user_resources_resources.rb b/lib/authress_sdk/models/user_resources_resources.rb similarity index 69% rename from lib/swagger_client/models/user_resources_resources.rb rename to lib/authress_sdk/models/user_resources_resources.rb index 2072580..51be595 100644 --- a/lib/swagger_client/models/user_resources_resources.rb +++ b/lib/authress_sdk/models/user_resources_resources.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class UserResourcesResources # The resourceUri that matches the requested resourceUri that the user has access to. attr_accessor :resource_uri @@ -40,13 +33,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::UserResourcesResources` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::UserResourcesResources` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::UserResourcesResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::UserResourcesResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -155,7 +148,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/user_token.rb b/lib/authress_sdk/models/user_token.rb similarity index 73% rename from lib/swagger_client/models/user_token.rb rename to lib/authress_sdk/models/user_token.rb index 5e1a246..333a786 100644 --- a/lib/swagger_client/models/user_token.rb +++ b/lib/authress_sdk/models/user_token.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A JWT token with represents the user. class UserToken attr_accessor :account @@ -58,13 +51,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::UserToken` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::UserToken` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::UserToken`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::UserToken`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -208,7 +201,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/user_token_links.rb b/lib/authress_sdk/models/user_token_links.rb similarity index 69% rename from lib/swagger_client/models/user_token_links.rb rename to lib/authress_sdk/models/user_token_links.rb index a2cdc5d..fe2de35 100644 --- a/lib/swagger_client/models/user_token_links.rb +++ b/lib/authress_sdk/models/user_token_links.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class UserTokenLinks attr_accessor :_self @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::UserTokenLinks` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::UserTokenLinks` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::UserTokenLinks`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::UserTokenLinks`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -159,7 +152,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/user_token_links_self.rb b/lib/authress_sdk/models/user_token_links_self.rb similarity index 70% rename from lib/swagger_client/models/user_token_links_self.rb rename to lib/authress_sdk/models/user_token_links_self.rb index 52cd2be..06e093d 100644 --- a/lib/swagger_client/models/user_token_links_self.rb +++ b/lib/authress_sdk/models/user_token_links_self.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A self link pointing to this token to be able to disable it or get its current configuration. class UserTokenLinksSelf # The absolute url pointing to the reference resource. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::UserTokenLinksSelf` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::UserTokenLinksSelf` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::UserTokenLinksSelf`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::UserTokenLinksSelf`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -171,7 +164,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1clients_options.rb b/lib/authress_sdk/models/v1clients_options.rb similarity index 71% rename from lib/swagger_client/models/v1clients_options.rb rename to lib/authress_sdk/models/v1clients_options.rb index d18af99..a07fe85 100644 --- a/lib/swagger_client/models/v1clients_options.rb +++ b/lib/authress_sdk/models/v1clients_options.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A map of client specific options class V1clientsOptions # Grant the client access to verify authorization on behalf of any user. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1clientsOptions` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1clientsOptions` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1clientsOptions`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1clientsOptions`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -166,7 +159,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1records_account.rb b/lib/authress_sdk/models/v1records_account.rb similarity index 69% rename from lib/swagger_client/models/v1records_account.rb rename to lib/authress_sdk/models/v1records_account.rb index 886f0e8..4d53bbe 100644 --- a/lib/swagger_client/models/v1records_account.rb +++ b/lib/authress_sdk/models/v1records_account.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class V1recordsAccount attr_accessor :account_id @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1recordsAccount` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1recordsAccount` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1recordsAccount`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1recordsAccount`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -159,7 +152,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1records_links.rb b/lib/authress_sdk/models/v1records_links.rb similarity index 69% rename from lib/swagger_client/models/v1records_links.rb rename to lib/authress_sdk/models/v1records_links.rb index 503d714..ce3bd2b 100644 --- a/lib/swagger_client/models/v1records_links.rb +++ b/lib/authress_sdk/models/v1records_links.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class V1recordsLinks attr_accessor :_self @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1recordsLinks` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1recordsLinks` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1recordsLinks`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1recordsLinks`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -159,7 +152,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1records_links_self.rb b/lib/authress_sdk/models/v1records_links_self.rb similarity index 70% rename from lib/swagger_client/models/v1records_links_self.rb rename to lib/authress_sdk/models/v1records_links_self.rb index 68239ad..02637a3 100644 --- a/lib/swagger_client/models/v1records_links_self.rb +++ b/lib/authress_sdk/models/v1records_links_self.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A self link pointing to this request url class V1recordsLinksSelf # The absolute url pointing to the reference resource. @@ -46,13 +39,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1recordsLinksSelf` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1recordsLinksSelf` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1recordsLinksSelf`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1recordsLinksSelf`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -171,7 +164,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1records_users.rb b/lib/authress_sdk/models/v1records_users.rb similarity index 69% rename from lib/swagger_client/models/v1records_users.rb rename to lib/authress_sdk/models/v1records_users.rb index acffb64..f565fad 100644 --- a/lib/swagger_client/models/v1records_users.rb +++ b/lib/authress_sdk/models/v1records_users.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # A user object that identifies a user. class V1recordsUsers attr_accessor :user_id @@ -40,13 +33,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1recordsUsers` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1recordsUsers` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1recordsUsers`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1recordsUsers`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -160,7 +153,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1resourcesresource_uri_permissions.rb b/lib/authress_sdk/models/v1resourcesresource_uri_permissions.rb similarity index 73% rename from lib/swagger_client/models/v1resourcesresource_uri_permissions.rb rename to lib/authress_sdk/models/v1resourcesresource_uri_permissions.rb index 7d01084..1332818 100644 --- a/lib/swagger_client/models/v1resourcesresource_uri_permissions.rb +++ b/lib/authress_sdk/models/v1resourcesresource_uri_permissions.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class V1resourcesresourceUriPermissions attr_accessor :action @@ -65,13 +58,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1resourcesresourceUriPermissions` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1resourcesresourceUriPermissions` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1resourcesresourceUriPermissions`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1resourcesresourceUriPermissions`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -207,7 +200,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/permission_object.rb b/lib/authress_sdk/models/v1roles_permissions.rb similarity index 75% rename from lib/swagger_client/models/permission_object.rb rename to lib/authress_sdk/models/v1roles_permissions.rb index a8c2715..9392e4e 100644 --- a/lib/swagger_client/models/permission_object.rb +++ b/lib/authress_sdk/models/v1roles_permissions.rb @@ -1,19 +1,12 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk # The collective action and associate grants on a permission - class PermissionObject + class V1rolesPermissions # The action the permission grants, can be scoped using `:` and parent actions imply sub-resource permissions, action:* or action implies action:sub-action. This property is case-insensitive, it will always be cast to lowercase before comparing actions to user permissions. attr_accessor :action @@ -56,13 +49,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::PermissionObject` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1rolesPermissions` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::PermissionObject`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1rolesPermissions`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -206,7 +199,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1usersuser_idresourcesresource_urimetadata_account.rb b/lib/authress_sdk/models/v1usersuser_idresourcesresource_urimetadata_account.rb similarity index 68% rename from lib/swagger_client/models/v1usersuser_idresourcesresource_urimetadata_account.rb rename to lib/authress_sdk/models/v1usersuser_idresourcesresource_urimetadata_account.rb index e6158e7..787fb06 100644 --- a/lib/swagger_client/models/v1usersuser_idresourcesresource_urimetadata_account.rb +++ b/lib/authress_sdk/models/v1usersuser_idresourcesresource_urimetadata_account.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class V1usersuserIdresourcesresourceUrimetadataAccount attr_accessor :account_id @@ -39,13 +32,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1usersuserIdresourcesresourceUrimetadataAccount` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1usersuserIdresourcesresourceUrimetadataAccount` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1usersuserIdresourcesresourceUrimetadataAccount`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1usersuserIdresourcesresourceUrimetadataAccount`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -154,7 +147,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1usersuser_idtokens_resources.rb b/lib/authress_sdk/models/v1usersuser_idtokens_resources.rb similarity index 69% rename from lib/swagger_client/models/v1usersuser_idtokens_resources.rb rename to lib/authress_sdk/models/v1usersuser_idtokens_resources.rb index 2410835..20ba0fc 100644 --- a/lib/swagger_client/models/v1usersuser_idtokens_resources.rb +++ b/lib/authress_sdk/models/v1usersuser_idtokens_resources.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class V1usersuserIdtokensResources # A resource path which can be top level, fully qualified, or end with a *. Parent resources imply permissions to sub-resources. attr_accessor :resource_uri @@ -40,13 +33,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1usersuserIdtokensResources` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1usersuserIdtokensResources` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1usersuserIdtokensResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1usersuserIdtokensResources`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -160,7 +153,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/swagger_client/models/v1usersuser_idtokens_statements.rb b/lib/authress_sdk/models/v1usersuser_idtokens_statements.rb similarity index 70% rename from lib/swagger_client/models/v1usersuser_idtokens_statements.rb rename to lib/authress_sdk/models/v1usersuser_idtokens_statements.rb index 4febd87..5d1fee0 100644 --- a/lib/swagger_client/models/v1usersuser_idtokens_statements.rb +++ b/lib/authress_sdk/models/v1usersuser_idtokens_statements.rb @@ -1,17 +1,10 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'date' -module SwaggerClient +module AuthressSdk class V1usersuserIdtokensStatements attr_accessor :roles @@ -43,13 +36,13 @@ def self.openapi_nullable # @param [Hash] attributes Model attributes in the form of hash def initialize(attributes = {}) if (!attributes.is_a?(Hash)) - fail ArgumentError, "The input argument (attributes) must be a hash in `SwaggerClient::V1usersuserIdtokensStatements` initialize method" + fail ArgumentError, "The input argument (attributes) must be a hash in `AuthressSdk::V1usersuserIdtokensStatements` initialize method" end # check to see if the attribute exists and convert string to symbol for hash key attributes = attributes.each_with_object({}) { |(k, v), h| if (!self.class.attribute_map.key?(k.to_sym)) - fail ArgumentError, "`#{k}` is not a valid attribute in `SwaggerClient::V1usersuserIdtokensStatements`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect + fail ArgumentError, "`#{k}` is not a valid attribute in `AuthressSdk::V1usersuserIdtokensStatements`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect end h[k.to_sym] = v } @@ -177,7 +170,7 @@ def _deserialize(type, value) end end else # model - SwaggerClient.const_get(type).build_from_hash(value) + AuthressSdk.const_get(type).build_from_hash(value) end end diff --git a/lib/authress_sdk/service_client_token_provider.rb b/lib/authress_sdk/service_client_token_provider.rb new file mode 100644 index 0000000..9a25c17 --- /dev/null +++ b/lib/authress_sdk/service_client_token_provider.rb @@ -0,0 +1,18 @@ +require 'date' +require 'json' +require 'logger' +require 'tempfile' +require 'typhoeus' +require 'uri' + +module AuthressSdk + class ServiceClientTokenProvider + def initialize(client_access_key) + @client_access_key = client_access_key + end + + def get_token() + @client_access_key + end + end +end diff --git a/lib/swagger_client.rb b/lib/swagger_client.rb deleted file mode 100644 index 46315ed..0000000 --- a/lib/swagger_client.rb +++ /dev/null @@ -1,30 +0,0 @@ -=begin -#Authress - -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 -=end - -Dir["#{File.expand_path(File.dirname(__FILE__))}/**/*.rb"].each{|f| require f} - -module SwaggerClient - class << self - # Customize default settings for the SDK using block. - # SwaggerClient.configure do |config| - # config.username = "xxx" - # config.password = "xxx" - # end - # If no block given, return the default Configuration object. - def configure - if block_given? - yield(Configuration.default) - else - Configuration.default - end - end - end -end diff --git a/lib/swagger_client/api_error.rb b/lib/swagger_client/api_error.rb deleted file mode 100644 index 26f97bb..0000000 --- a/lib/swagger_client/api_error.rb +++ /dev/null @@ -1,57 +0,0 @@ -=begin -#Authress - -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 -=end - -module SwaggerClient - class ApiError < StandardError - attr_reader :code, :response_headers, :response_body - - # Usage examples: - # ApiError.new - # ApiError.new("message") - # ApiError.new(:code => 500, :response_headers => {}, :response_body => "") - # ApiError.new(:code => 404, :message => "Not Found") - def initialize(arg = nil) - if arg.is_a? Hash - if arg.key?(:message) || arg.key?('message') - super(arg[:message] || arg['message']) - else - super arg - end - - arg.each do |k, v| - instance_variable_set "@#{k}", v - end - else - super arg - end - end - - # Override to_s to display a friendly error message - def to_s - message - end - - def message - if @message.nil? - msg = "Error message: the server returns an error" - else - msg = @message - end - - msg += "\nHTTP status code: #{code}" if code - msg += "\nResponse headers: #{response_headers}" if response_headers - msg += "\nResponse body: #{response_body}" if response_body - - msg - end - - end -end diff --git a/lib/swagger_client/configuration.rb b/lib/swagger_client/configuration.rb deleted file mode 100644 index 143118e..0000000 --- a/lib/swagger_client/configuration.rb +++ /dev/null @@ -1,205 +0,0 @@ -=begin -#Authress - -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 -=end - -module SwaggerClient - class Configuration - # Defines url scheme - attr_accessor :scheme - - # Defines url host - attr_accessor :host - - # Defines url base path - attr_accessor :base_path - - # Defines API keys used with API Key authentications. - # - # @return [Hash] key: parameter name, value: parameter value (API key) - # - # @example parameter name is "api_key", API key is "xxx" (e.g. "api_key=xxx" in query string) - # config.api_key['api_key'] = 'xxx' - attr_accessor :api_key - - # Defines API key prefixes used with API Key authentications. - # - # @return [Hash] key: parameter name, value: API key prefix - # - # @example parameter name is "Authorization", API key prefix is "Token" (e.g. "Authorization: Token xxx" in headers) - # config.api_key_prefix['api_key'] = 'Token' - attr_accessor :api_key_prefix - - # Defines the username used with HTTP basic authentication. - # - # @return [String] - attr_accessor :username - - # Defines the password used with HTTP basic authentication. - # - # @return [String] - attr_accessor :password - - # Defines the access token (Bearer) used with OAuth2. - attr_accessor :access_token - - # Set this to enable/disable debugging. When enabled (set to true), HTTP request/response - # details will be logged with `logger.debug` (see the `logger` attribute). - # Default to false. - # - # @return [true, false] - attr_accessor :debugging - - # Defines the logger used for debugging. - # Default to `Rails.logger` (when in Rails) or logging to STDOUT. - # - # @return [#debug] - attr_accessor :logger - - # Defines the temporary folder to store downloaded files - # (for API endpoints that have file response). - # Default to use `Tempfile`. - # - # @return [String] - attr_accessor :temp_folder_path - - # The time limit for HTTP request in seconds. - # Default to 0 (never times out). - attr_accessor :timeout - - # Set this to false to skip client side validation in the operation. - # Default to true. - # @return [true, false] - attr_accessor :client_side_validation - - ### TLS/SSL setting - # Set this to false to skip verifying SSL certificate when calling API from https server. - # Default to true. - # - # @note Do NOT set it to false in production code, otherwise you would face multiple types of cryptographic attacks. - # - # @return [true, false] - attr_accessor :verify_ssl - - ### TLS/SSL setting - # Set this to false to skip verifying SSL host name - # Default to true. - # - # @note Do NOT set it to false in production code, otherwise you would face multiple types of cryptographic attacks. - # - # @return [true, false] - attr_accessor :verify_ssl_host - - ### TLS/SSL setting - # Set this to customize the certificate file to verify the peer. - # - # @return [String] the path to the certificate file - # - # @see The `cainfo` option of Typhoeus, `--cert` option of libcurl. Related source code: - # https://github.com/typhoeus/typhoeus/blob/master/lib/typhoeus/easy_factory.rb#L145 - attr_accessor :ssl_ca_cert - - ### TLS/SSL setting - # Client certificate file (for client certificate) - attr_accessor :cert_file - - ### TLS/SSL setting - # Client private key file (for client certificate) - attr_accessor :key_file - - # Set this to customize parameters encoding of array parameter with multi collectionFormat. - # Default to nil. - # - # @see The params_encoding option of Ethon. Related source code: - # https://github.com/typhoeus/ethon/blob/master/lib/ethon/easy/queryable.rb#L96 - attr_accessor :params_encoding - - attr_accessor :inject_format - - attr_accessor :force_ending_format - - def initialize - @scheme = 'http' - @host = 'api.authress.io' - @base_path = '/' - @api_key = {} - @api_key_prefix = {} - @timeout = 0 - @client_side_validation = true - @verify_ssl = true - @verify_ssl_host = true - @params_encoding = nil - @cert_file = nil - @key_file = nil - @debugging = false - @inject_format = false - @force_ending_format = false - @logger = defined?(Rails) ? Rails.logger : Logger.new(STDOUT) - - yield(self) if block_given? - end - - # The default Configuration object. - def self.default - @@default ||= Configuration.new - end - - def configure - yield(self) if block_given? - end - - def scheme=(scheme) - # remove :// from scheme - @scheme = scheme.sub(/:\/\//, '') - end - - def host=(host) - # remove http(s):// and anything after a slash - @host = host.sub(/https?:\/\//, '').split('/').first - end - - def base_path=(base_path) - # Add leading and trailing slashes to base_path - @base_path = "/#{base_path}".gsub(/\/+/, '/') - @base_path = '' if @base_path == '/' - end - - def base_url - "#{scheme}://#{[host, base_path].join('/').gsub(/\/+/, '/')}".sub(/\/+\z/, '') - end - - # Gets API key (with prefix if set). - # @param [String] param_name the parameter name of API key auth - def api_key_with_prefix(param_name) - if @api_key_prefix[param_name] - "#{@api_key_prefix[param_name]} #{@api_key[param_name]}" - else - @api_key[param_name] - end - end - - # Gets Basic Auth token string - def basic_auth_token - 'Basic ' + ["#{username}:#{password}"].pack('m').delete("\r\n") - end - - # Returns Auth Settings hash for api client. - def auth_settings - { - 'oauth2' => - { - type: 'bearer', - in: 'header', - key: 'Authorization', - value: "Bearer #{access_token}" - }, - } - end - end -end diff --git a/lib/swagger_client/version.rb b/lib/swagger_client/version.rb deleted file mode 100644 index 120ec8d..0000000 --- a/lib/swagger_client/version.rb +++ /dev/null @@ -1,14 +0,0 @@ -=begin -#Authress - -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 -=end - -module SwaggerClient - VERSION = '1.0.0' -end diff --git a/spec/api/access_records_api_spec.rb b/spec/api/access_records_api_spec.rb index dbb5064..ac5adae 100644 --- a/spec/api/access_records_api_spec.rb +++ b/spec/api/access_records_api_spec.rb @@ -1,24 +1,17 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' -# Unit tests for SwaggerClient::AccessRecordsApi -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::AccessRecordsApi + # Please update as you see appropriate describe 'AccessRecordsApi' do before do # run before each test - @instance = SwaggerClient::AccessRecordsApi.new + @instance = AuthressSdk::AccessRecordsApi.new end after do @@ -27,7 +20,7 @@ describe 'test an instance of AccessRecordsApi' do it 'should create an instance of AccessRecordsApi' do - expect(@instance).to be_instance_of(SwaggerClient::AccessRecordsApi) + expect(@instance).to be_instance_of(AuthressSdk::AccessRecordsApi) end end diff --git a/spec/api/accounts_api_spec.rb b/spec/api/accounts_api_spec.rb index 9b21848..ae559fd 100644 --- a/spec/api/accounts_api_spec.rb +++ b/spec/api/accounts_api_spec.rb @@ -1,24 +1,17 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' -# Unit tests for SwaggerClient::AccountsApi -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::AccountsApi + # Please update as you see appropriate describe 'AccountsApi' do before do # run before each test - @instance = SwaggerClient::AccountsApi.new + @instance = AuthressSdk::AccountsApi.new end after do @@ -27,7 +20,7 @@ describe 'test an instance of AccountsApi' do it 'should create an instance of AccountsApi' do - expect(@instance).to be_instance_of(SwaggerClient::AccountsApi) + expect(@instance).to be_instance_of(AuthressSdk::AccountsApi) end end diff --git a/spec/api/metadata_api_spec.rb b/spec/api/metadata_api_spec.rb index 77137ff..8442565 100644 --- a/spec/api/metadata_api_spec.rb +++ b/spec/api/metadata_api_spec.rb @@ -1,24 +1,17 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' -# Unit tests for SwaggerClient::MetadataApi -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::MetadataApi + # Please update as you see appropriate describe 'MetadataApi' do before do # run before each test - @instance = SwaggerClient::MetadataApi.new + @instance = AuthressSdk::MetadataApi.new end after do @@ -27,7 +20,7 @@ describe 'test an instance of MetadataApi' do it 'should create an instance of MetadataApi' do - expect(@instance).to be_instance_of(SwaggerClient::MetadataApi) + expect(@instance).to be_instance_of(AuthressSdk::MetadataApi) end end diff --git a/spec/api/resource_permissions_api_spec.rb b/spec/api/resource_permissions_api_spec.rb index e789033..aa8b35c 100644 --- a/spec/api/resource_permissions_api_spec.rb +++ b/spec/api/resource_permissions_api_spec.rb @@ -1,24 +1,17 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' -# Unit tests for SwaggerClient::ResourcePermissionsApi -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ResourcePermissionsApi + # Please update as you see appropriate describe 'ResourcePermissionsApi' do before do # run before each test - @instance = SwaggerClient::ResourcePermissionsApi.new + @instance = AuthressSdk::ResourcePermissionsApi.new end after do @@ -27,7 +20,7 @@ describe 'test an instance of ResourcePermissionsApi' do it 'should create an instance of ResourcePermissionsApi' do - expect(@instance).to be_instance_of(SwaggerClient::ResourcePermissionsApi) + expect(@instance).to be_instance_of(AuthressSdk::ResourcePermissionsApi) end end diff --git a/spec/api/roles_api_spec.rb b/spec/api/roles_api_spec.rb index 1a02ca6..01a8765 100644 --- a/spec/api/roles_api_spec.rb +++ b/spec/api/roles_api_spec.rb @@ -1,24 +1,17 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' -# Unit tests for SwaggerClient::RolesApi -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::RolesApi + # Please update as you see appropriate describe 'RolesApi' do before do # run before each test - @instance = SwaggerClient::RolesApi.new + @instance = AuthressSdk::RolesApi.new end after do @@ -27,7 +20,7 @@ describe 'test an instance of RolesApi' do it 'should create an instance of RolesApi' do - expect(@instance).to be_instance_of(SwaggerClient::RolesApi) + expect(@instance).to be_instance_of(AuthressSdk::RolesApi) end end diff --git a/spec/api/service_clients_api_spec.rb b/spec/api/service_clients_api_spec.rb index 0dd88dc..3c9790d 100644 --- a/spec/api/service_clients_api_spec.rb +++ b/spec/api/service_clients_api_spec.rb @@ -1,24 +1,17 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' -# Unit tests for SwaggerClient::ServiceClientsApi -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ServiceClientsApi + # Please update as you see appropriate describe 'ServiceClientsApi' do before do # run before each test - @instance = SwaggerClient::ServiceClientsApi.new + @instance = AuthressSdk::ServiceClientsApi.new end after do @@ -27,7 +20,7 @@ describe 'test an instance of ServiceClientsApi' do it 'should create an instance of ServiceClientsApi' do - expect(@instance).to be_instance_of(SwaggerClient::ServiceClientsApi) + expect(@instance).to be_instance_of(AuthressSdk::ServiceClientsApi) end end diff --git a/spec/api/user_permissions_api_spec.rb b/spec/api/user_permissions_api_spec.rb index e8055a3..f9d60e9 100644 --- a/spec/api/user_permissions_api_spec.rb +++ b/spec/api/user_permissions_api_spec.rb @@ -1,24 +1,17 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' -# Unit tests for SwaggerClient::UserPermissionsApi -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::UserPermissionsApi + # Please update as you see appropriate describe 'UserPermissionsApi' do before do # run before each test - @instance = SwaggerClient::UserPermissionsApi.new + @instance = AuthressSdk::UserPermissionsApi.new end after do @@ -27,7 +20,7 @@ describe 'test an instance of UserPermissionsApi' do it 'should create an instance of UserPermissionsApi' do - expect(@instance).to be_instance_of(SwaggerClient::UserPermissionsApi) + expect(@instance).to be_instance_of(AuthressSdk::UserPermissionsApi) end end diff --git a/spec/api_client_spec.rb b/spec/api_client_spec.rb index 6f9616f..e3b743c 100644 --- a/spec/api_client_spec.rb +++ b/spec/api_client_spec.rb @@ -1,117 +1,34 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' -describe SwaggerClient::ApiClient do - context 'initialization' do - context 'URL stuff' do - context 'host' do - it 'removes http from host' do - SwaggerClient.configure { |c| c.host = 'http://example.com' } - expect(SwaggerClient::Configuration.default.host).to eq('example.com') - end - - it 'removes https from host' do - SwaggerClient.configure { |c| c.host = 'https://wookiee.com' } - expect(SwaggerClient::ApiClient.default.config.host).to eq('wookiee.com') - end - - it 'removes trailing path from host' do - SwaggerClient.configure { |c| c.host = 'hobo.com/v4' } - expect(SwaggerClient::Configuration.default.host).to eq('hobo.com') - end - end - - context 'base_path' do - it "prepends a slash to base_path" do - SwaggerClient.configure { |c| c.base_path = 'v4/dog' } - expect(SwaggerClient::Configuration.default.base_path).to eq('/v4/dog') - end - - it "doesn't prepend a slash if one is already there" do - SwaggerClient.configure { |c| c.base_path = '/v4/dog' } - expect(SwaggerClient::Configuration.default.base_path).to eq('/v4/dog') - end - - it "ends up as a blank string if nil" do - SwaggerClient.configure { |c| c.base_path = nil } - expect(SwaggerClient::Configuration.default.base_path).to eq('') - end - end - end - end - - describe 'params_encoding in #build_request' do - let(:config) { SwaggerClient::Configuration.new } - let(:api_client) { SwaggerClient::ApiClient.new(config) } - - it 'defaults to nil' do - expect(SwaggerClient::Configuration.default.params_encoding).to eq(nil) - expect(config.params_encoding).to eq(nil) - - request = api_client.build_request(:get, '/test') - expect(request.options[:params_encoding]).to eq(nil) - end - - it 'can be customized' do - config.params_encoding = :multi - request = api_client.build_request(:get, '/test') - expect(request.options[:params_encoding]).to eq(:multi) - end - end - - describe 'timeout in #build_request' do - let(:config) { SwaggerClient::Configuration.new } - let(:api_client) { SwaggerClient::ApiClient.new(config) } - - it 'defaults to 0' do - expect(SwaggerClient::Configuration.default.timeout).to eq(0) - expect(config.timeout).to eq(0) - - request = api_client.build_request(:get, '/test') - expect(request.options[:timeout]).to eq(0) - end - - it 'can be customized' do - config.timeout = 100 - request = api_client.build_request(:get, '/test') - expect(request.options[:timeout]).to eq(100) - end - end - +describe AuthressSdk::AuthressClient do describe '#deserialize' do it "handles Array" do - api_client = SwaggerClient::ApiClient.new + authress_client = AuthressSdk::AuthressClient.new headers = { 'Content-Type' => 'application/json' } response = double('response', headers: headers, body: '[12, 34]') - data = api_client.deserialize(response, 'Array') + data = authress_client.deserialize(response, 'Array') expect(data).to be_instance_of(Array) expect(data).to eq([12, 34]) end it 'handles Array>' do - api_client = SwaggerClient::ApiClient.new + authress_client = AuthressSdk::AuthressClient.new headers = { 'Content-Type' => 'application/json' } response = double('response', headers: headers, body: '[[12, 34], [56]]') - data = api_client.deserialize(response, 'Array>') + data = authress_client.deserialize(response, 'Array>') expect(data).to be_instance_of(Array) expect(data).to eq([[12, 34], [56]]) end it 'handles Hash' do - api_client = SwaggerClient::ApiClient.new + authress_client = AuthressSdk::AuthressClient.new headers = { 'Content-Type' => 'application/json' } response = double('response', headers: headers, body: '{"message": "Hello"}') - data = api_client.deserialize(response, 'Hash') + data = authress_client.deserialize(response, 'Hash') expect(data).to be_instance_of(Hash) expect(data).to eq(:message => 'Hello') end @@ -120,106 +37,106 @@ describe "#object_to_hash" do it 'ignores nils and includes empty arrays' do # uncomment below to test object_to_hash for model - # api_client = SwaggerClient::ApiClient.new - # _model = SwaggerClient::ModelName.new + # authress_client = AuthressSdk::AuthressClient.new + # _model = AuthressSdk::ModelName.new # update the model attribute below # _model.id = 1 # update the expected value (hash) below # expected = {id: 1, name: '', tags: []} - # expect(api_client.object_to_hash(_model)).to eq(expected) + # expect(authress_client.object_to_hash(_model)).to eq(expected) end end describe '#build_collection_param' do let(:param) { ['aa', 'bb', 'cc'] } - let(:api_client) { SwaggerClient::ApiClient.new } + let(:authress_client) { AuthressSdk::AuthressClient.new } it 'works for csv' do - expect(api_client.build_collection_param(param, :csv)).to eq('aa,bb,cc') + expect(authress_client.build_collection_param(param, :csv)).to eq('aa,bb,cc') end it 'works for ssv' do - expect(api_client.build_collection_param(param, :ssv)).to eq('aa bb cc') + expect(authress_client.build_collection_param(param, :ssv)).to eq('aa bb cc') end it 'works for tsv' do - expect(api_client.build_collection_param(param, :tsv)).to eq("aa\tbb\tcc") + expect(authress_client.build_collection_param(param, :tsv)).to eq("aa\tbb\tcc") end it 'works for pipes' do - expect(api_client.build_collection_param(param, :pipes)).to eq('aa|bb|cc') + expect(authress_client.build_collection_param(param, :pipes)).to eq('aa|bb|cc') end it 'works for multi' do - expect(api_client.build_collection_param(param, :multi)).to eq(['aa', 'bb', 'cc']) + expect(authress_client.build_collection_param(param, :multi)).to eq(['aa', 'bb', 'cc']) end it 'fails for invalid collection format' do - expect(proc { api_client.build_collection_param(param, :INVALID) }).to raise_error(RuntimeError, 'unknown collection format: :INVALID') + expect(proc { authress_client.build_collection_param(param, :INVALID) }).to raise_error(RuntimeError, 'unknown collection format: :INVALID') end end describe '#json_mime?' do - let(:api_client) { SwaggerClient::ApiClient.new } + let(:authress_client) { AuthressSdk::AuthressClient.new } it 'works' do - expect(api_client.json_mime?(nil)).to eq false - expect(api_client.json_mime?('')).to eq false + expect(authress_client.json_mime?(nil)).to eq false + expect(authress_client.json_mime?('')).to eq false - expect(api_client.json_mime?('application/json')).to eq true - expect(api_client.json_mime?('application/json; charset=UTF8')).to eq true - expect(api_client.json_mime?('APPLICATION/JSON')).to eq true + expect(authress_client.json_mime?('application/json')).to eq true + expect(authress_client.json_mime?('application/json; charset=UTF8')).to eq true + expect(authress_client.json_mime?('APPLICATION/JSON')).to eq true - expect(api_client.json_mime?('application/xml')).to eq false - expect(api_client.json_mime?('text/plain')).to eq false - expect(api_client.json_mime?('application/jsonp')).to eq false + expect(authress_client.json_mime?('application/xml')).to eq false + expect(authress_client.json_mime?('text/plain')).to eq false + expect(authress_client.json_mime?('application/jsonp')).to eq false end end describe '#select_header_accept' do - let(:api_client) { SwaggerClient::ApiClient.new } + let(:authress_client) { AuthressSdk::AuthressClient.new } it 'works' do - expect(api_client.select_header_accept(nil)).to be_nil - expect(api_client.select_header_accept([])).to be_nil + expect(authress_client.select_header_accept(nil)).to be_nil + expect(authress_client.select_header_accept([])).to be_nil - expect(api_client.select_header_accept(['application/json'])).to eq('application/json') - expect(api_client.select_header_accept(['application/xml', 'application/json; charset=UTF8'])).to eq('application/json; charset=UTF8') - expect(api_client.select_header_accept(['APPLICATION/JSON', 'text/html'])).to eq('APPLICATION/JSON') + expect(authress_client.select_header_accept(['application/json'])).to eq('application/json') + expect(authress_client.select_header_accept(['application/xml', 'application/json; charset=UTF8'])).to eq('application/json; charset=UTF8') + expect(authress_client.select_header_accept(['APPLICATION/JSON', 'text/html'])).to eq('APPLICATION/JSON') - expect(api_client.select_header_accept(['application/xml'])).to eq('application/xml') - expect(api_client.select_header_accept(['text/html', 'application/xml'])).to eq('text/html,application/xml') + expect(authress_client.select_header_accept(['application/xml'])).to eq('application/xml') + expect(authress_client.select_header_accept(['text/html', 'application/xml'])).to eq('text/html,application/xml') end end describe '#select_header_content_type' do - let(:api_client) { SwaggerClient::ApiClient.new } + let(:authress_client) { AuthressSdk::AuthressClient.new } it 'works' do - expect(api_client.select_header_content_type(nil)).to eq('application/json') - expect(api_client.select_header_content_type([])).to eq('application/json') - - expect(api_client.select_header_content_type(['application/json'])).to eq('application/json') - expect(api_client.select_header_content_type(['application/xml', 'application/json; charset=UTF8'])).to eq('application/json; charset=UTF8') - expect(api_client.select_header_content_type(['APPLICATION/JSON', 'text/html'])).to eq('APPLICATION/JSON') - expect(api_client.select_header_content_type(['application/xml'])).to eq('application/xml') - expect(api_client.select_header_content_type(['text/plain', 'application/xml'])).to eq('text/plain') + expect(authress_client.select_header_content_type(nil)).to eq('application/json') + expect(authress_client.select_header_content_type([])).to eq('application/json') + + expect(authress_client.select_header_content_type(['application/json'])).to eq('application/json') + expect(authress_client.select_header_content_type(['application/xml', 'application/json; charset=UTF8'])).to eq('application/json; charset=UTF8') + expect(authress_client.select_header_content_type(['APPLICATION/JSON', 'text/html'])).to eq('APPLICATION/JSON') + expect(authress_client.select_header_content_type(['application/xml'])).to eq('application/xml') + expect(authress_client.select_header_content_type(['text/plain', 'application/xml'])).to eq('text/plain') end end describe '#sanitize_filename' do - let(:api_client) { SwaggerClient::ApiClient.new } + let(:authress_client) { AuthressSdk::AuthressClient.new } it 'works' do - expect(api_client.sanitize_filename('sun')).to eq('sun') - expect(api_client.sanitize_filename('sun.gif')).to eq('sun.gif') - expect(api_client.sanitize_filename('../sun.gif')).to eq('sun.gif') - expect(api_client.sanitize_filename('/var/tmp/sun.gif')).to eq('sun.gif') - expect(api_client.sanitize_filename('./sun.gif')).to eq('sun.gif') - expect(api_client.sanitize_filename('..\sun.gif')).to eq('sun.gif') - expect(api_client.sanitize_filename('\var\tmp\sun.gif')).to eq('sun.gif') - expect(api_client.sanitize_filename('c:\var\tmp\sun.gif')).to eq('sun.gif') - expect(api_client.sanitize_filename('.\sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('sun')).to eq('sun') + expect(authress_client.sanitize_filename('sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('../sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('/var/tmp/sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('./sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('..\sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('\var\tmp\sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('c:\var\tmp\sun.gif')).to eq('sun.gif') + expect(authress_client.sanitize_filename('.\sun.gif')).to eq('sun.gif') end end end diff --git a/spec/configuration_spec.rb b/spec/configuration_spec.rb deleted file mode 100644 index 2e9c510..0000000 --- a/spec/configuration_spec.rb +++ /dev/null @@ -1,41 +0,0 @@ -=begin -#Authress - -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 -=end - -require 'spec_helper' - -describe SwaggerClient::Configuration do - let(:config) { SwaggerClient::Configuration.default } - - before(:each) do - # uncomment below to setup host and base_path - # require 'URI' - # uri = URI.parse("/") - # SwaggerClient.configure do |c| - # c.host = uri.host - # c.base_path = uri.path - # end - end - - describe '#base_url' do - it 'should have the default value' do - # uncomment below to test default value of the base path - # expect(config.base_url).to eq("/") - end - - it 'should remove trailing slashes' do - [nil, '', '/', '//'].each do |base_path| - config.base_path = base_path - # uncomment below to test trailing slashes - # expect(config.base_url).to eq("/") - end - end - end -end diff --git a/spec/constant_token_provider_spec.rb b/spec/constant_token_provider_spec.rb new file mode 100644 index 0000000..85c8d20 --- /dev/null +++ b/spec/constant_token_provider_spec.rb @@ -0,0 +1,16 @@ +=begin + +=end + +require 'spec_helper' + +describe AuthressSdk::ConstantTokenProvider do + describe 'tokenProvider()' do + it "Generates service client access token" do + access_token = 'test-token' + tokenProvider = AuthressSdk::ConstantTokenProvider.new(access_token) + result = tokenProvider.get_token() + expect(result).to eq(access_token); + end + end +end diff --git a/spec/models/access_record_collection_records_spec.rb b/spec/models/access_record_collection_records_spec.rb index dd1b50c..d952e63 100644 --- a/spec/models/access_record_collection_records_spec.rb +++ b/spec/models/access_record_collection_records_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::AccessRecordCollectionRecords -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::AccessRecordCollectionRecords + # Please update as you see appropriate describe 'AccessRecordCollectionRecords' do before do # run before each test - @instance = SwaggerClient::AccessRecordCollectionRecords.new + @instance = AuthressSdk::AccessRecordCollectionRecords.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of AccessRecordCollectionRecords' do it 'should create an instance of AccessRecordCollectionRecords' do - expect(@instance).to be_instance_of(SwaggerClient::AccessRecordCollectionRecords) + expect(@instance).to be_instance_of(AuthressSdk::AccessRecordCollectionRecords) end end describe 'test attribute "record_id"' do diff --git a/spec/models/access_record_collection_spec.rb b/spec/models/access_record_collection_spec.rb index a9b19a1..15df033 100644 --- a/spec/models/access_record_collection_spec.rb +++ b/spec/models/access_record_collection_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::AccessRecordCollection -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::AccessRecordCollection + # Please update as you see appropriate describe 'AccessRecordCollection' do before do # run before each test - @instance = SwaggerClient::AccessRecordCollection.new + @instance = AuthressSdk::AccessRecordCollection.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of AccessRecordCollection' do it 'should create an instance of AccessRecordCollection' do - expect(@instance).to be_instance_of(SwaggerClient::AccessRecordCollection) + expect(@instance).to be_instance_of(AuthressSdk::AccessRecordCollection) end end describe 'test attribute "records"' do diff --git a/spec/models/access_record_spec.rb b/spec/models/access_record_spec.rb index e5e240a..b270b55 100644 --- a/spec/models/access_record_spec.rb +++ b/spec/models/access_record_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::AccessRecord -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::AccessRecord + # Please update as you see appropriate describe 'AccessRecord' do before do # run before each test - @instance = SwaggerClient::AccessRecord.new + @instance = AuthressSdk::AccessRecord.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of AccessRecord' do it 'should create an instance of AccessRecord' do - expect(@instance).to be_instance_of(SwaggerClient::AccessRecord) + expect(@instance).to be_instance_of(AuthressSdk::AccessRecord) end end describe 'test attribute "record_id"' do diff --git a/spec/models/account_collection_accounts_spec.rb b/spec/models/account_collection_accounts_spec.rb index 352d0df..771276a 100644 --- a/spec/models/account_collection_accounts_spec.rb +++ b/spec/models/account_collection_accounts_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::AccountCollectionAccounts -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::AccountCollectionAccounts + # Please update as you see appropriate describe 'AccountCollectionAccounts' do before do # run before each test - @instance = SwaggerClient::AccountCollectionAccounts.new + @instance = AuthressSdk::AccountCollectionAccounts.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of AccountCollectionAccounts' do it 'should create an instance of AccountCollectionAccounts' do - expect(@instance).to be_instance_of(SwaggerClient::AccountCollectionAccounts) + expect(@instance).to be_instance_of(AuthressSdk::AccountCollectionAccounts) end end describe 'test attribute "account_id"' do diff --git a/spec/models/account_collection_spec.rb b/spec/models/account_collection_spec.rb index c3a419b..c7d2e3b 100644 --- a/spec/models/account_collection_spec.rb +++ b/spec/models/account_collection_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::AccountCollection -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::AccountCollection + # Please update as you see appropriate describe 'AccountCollection' do before do # run before each test - @instance = SwaggerClient::AccountCollection.new + @instance = AuthressSdk::AccountCollection.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of AccountCollection' do it 'should create an instance of AccountCollection' do - expect(@instance).to be_instance_of(SwaggerClient::AccountCollection) + expect(@instance).to be_instance_of(AuthressSdk::AccountCollection) end end describe 'test attribute "accounts"' do diff --git a/spec/models/account_spec.rb b/spec/models/account_spec.rb index 9866ab5..04b5209 100644 --- a/spec/models/account_spec.rb +++ b/spec/models/account_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Account -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Account + # Please update as you see appropriate describe 'Account' do before do # run before each test - @instance = SwaggerClient::Account.new + @instance = AuthressSdk::Account.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Account' do it 'should create an instance of Account' do - expect(@instance).to be_instance_of(SwaggerClient::Account) + expect(@instance).to be_instance_of(AuthressSdk::Account) end end describe 'test attribute "account_id"' do diff --git a/spec/models/body_10_spec.rb b/spec/models/body_10_spec.rb index 195127b..ee20682 100644 --- a/spec/models/body_10_spec.rb +++ b/spec/models/body_10_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body10 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body10 + # Please update as you see appropriate describe 'Body10' do before do # run before each test - @instance = SwaggerClient::Body10.new + @instance = AuthressSdk::Body10.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body10' do it 'should create an instance of Body10' do - expect(@instance).to be_instance_of(SwaggerClient::Body10) + expect(@instance).to be_instance_of(AuthressSdk::Body10) end end describe 'test attribute "client_id"' do diff --git a/spec/models/body_11_spec.rb b/spec/models/body_11_spec.rb index 7b5f689..dba1976 100644 --- a/spec/models/body_11_spec.rb +++ b/spec/models/body_11_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body11 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body11 + # Please update as you see appropriate describe 'Body11' do before do # run before each test - @instance = SwaggerClient::Body11.new + @instance = AuthressSdk::Body11.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body11' do it 'should create an instance of Body11' do - expect(@instance).to be_instance_of(SwaggerClient::Body11) + expect(@instance).to be_instance_of(AuthressSdk::Body11) end end describe 'test attribute "client_id"' do diff --git a/spec/models/body_1_spec.rb b/spec/models/body_1_spec.rb index e73c735..3edd28a 100644 --- a/spec/models/body_1_spec.rb +++ b/spec/models/body_1_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body1 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body1 + # Please update as you see appropriate describe 'Body1' do before do # run before each test - @instance = SwaggerClient::Body1.new + @instance = AuthressSdk::Body1.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body1' do it 'should create an instance of Body1' do - expect(@instance).to be_instance_of(SwaggerClient::Body1) + expect(@instance).to be_instance_of(AuthressSdk::Body1) end end describe 'test attribute "statements"' do diff --git a/spec/models/body_2_spec.rb b/spec/models/body_2_spec.rb index 8487a90..d4f5b19 100644 --- a/spec/models/body_2_spec.rb +++ b/spec/models/body_2_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body2 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body2 + # Please update as you see appropriate describe 'Body2' do before do # run before each test - @instance = SwaggerClient::Body2.new + @instance = AuthressSdk::Body2.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body2' do it 'should create an instance of Body2' do - expect(@instance).to be_instance_of(SwaggerClient::Body2) + expect(@instance).to be_instance_of(AuthressSdk::Body2) end end describe 'test attribute "permissions"' do diff --git a/spec/models/body_3_spec.rb b/spec/models/body_3_spec.rb index a2f85e5..d41cd22 100644 --- a/spec/models/body_3_spec.rb +++ b/spec/models/body_3_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body3 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body3 + # Please update as you see appropriate describe 'Body3' do before do # run before each test - @instance = SwaggerClient::Body3.new + @instance = AuthressSdk::Body3.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body3' do it 'should create an instance of Body3' do - expect(@instance).to be_instance_of(SwaggerClient::Body3) + expect(@instance).to be_instance_of(AuthressSdk::Body3) end end describe 'test attribute "record_id"' do diff --git a/spec/models/body_4_spec.rb b/spec/models/body_4_spec.rb index ead261f..f80ff58 100644 --- a/spec/models/body_4_spec.rb +++ b/spec/models/body_4_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body4 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body4 + # Please update as you see appropriate describe 'Body4' do before do # run before each test - @instance = SwaggerClient::Body4.new + @instance = AuthressSdk::Body4.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body4' do it 'should create an instance of Body4' do - expect(@instance).to be_instance_of(SwaggerClient::Body4) + expect(@instance).to be_instance_of(AuthressSdk::Body4) end end describe 'test attribute "record_id"' do diff --git a/spec/models/body_5_spec.rb b/spec/models/body_5_spec.rb index 88e1d77..0deb081 100644 --- a/spec/models/body_5_spec.rb +++ b/spec/models/body_5_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body5 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body5 + # Please update as you see appropriate describe 'Body5' do before do # run before each test - @instance = SwaggerClient::Body5.new + @instance = AuthressSdk::Body5.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body5' do it 'should create an instance of Body5' do - expect(@instance).to be_instance_of(SwaggerClient::Body5) + expect(@instance).to be_instance_of(AuthressSdk::Body5) end end describe 'test attribute "email"' do diff --git a/spec/models/body_6_spec.rb b/spec/models/body_6_spec.rb index b7bdb96..7988cc9 100644 --- a/spec/models/body_6_spec.rb +++ b/spec/models/body_6_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body6 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body6 + # Please update as you see appropriate describe 'Body6' do before do # run before each test - @instance = SwaggerClient::Body6.new + @instance = AuthressSdk::Body6.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body6' do it 'should create an instance of Body6' do - expect(@instance).to be_instance_of(SwaggerClient::Body6) + expect(@instance).to be_instance_of(AuthressSdk::Body6) end end describe 'test attribute "role_id"' do diff --git a/spec/models/body_7_spec.rb b/spec/models/body_7_spec.rb index 235cedf..37a5fdb 100644 --- a/spec/models/body_7_spec.rb +++ b/spec/models/body_7_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body7 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body7 + # Please update as you see appropriate describe 'Body7' do before do # run before each test - @instance = SwaggerClient::Body7.new + @instance = AuthressSdk::Body7.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body7' do it 'should create an instance of Body7' do - expect(@instance).to be_instance_of(SwaggerClient::Body7) + expect(@instance).to be_instance_of(AuthressSdk::Body7) end end describe 'test attribute "role_id"' do diff --git a/spec/models/body_8_spec.rb b/spec/models/body_8_spec.rb index 4076dcd..05378f6 100644 --- a/spec/models/body_8_spec.rb +++ b/spec/models/body_8_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body8 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body8 + # Please update as you see appropriate describe 'Body8' do before do # run before each test - @instance = SwaggerClient::Body8.new + @instance = AuthressSdk::Body8.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body8' do it 'should create an instance of Body8' do - expect(@instance).to be_instance_of(SwaggerClient::Body8) + expect(@instance).to be_instance_of(AuthressSdk::Body8) end end describe 'test attribute "collection_resource"' do diff --git a/spec/models/body_9_spec.rb b/spec/models/body_9_spec.rb index 50acb66..9256321 100644 --- a/spec/models/body_9_spec.rb +++ b/spec/models/body_9_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body9 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body9 + # Please update as you see appropriate describe 'Body9' do before do # run before each test - @instance = SwaggerClient::Body9.new + @instance = AuthressSdk::Body9.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body9' do it 'should create an instance of Body9' do - expect(@instance).to be_instance_of(SwaggerClient::Body9) + expect(@instance).to be_instance_of(AuthressSdk::Body9) end end describe 'test attribute "jwt"' do diff --git a/spec/models/body_spec.rb b/spec/models/body_spec.rb index 671aea7..9e3f8fa 100644 --- a/spec/models/body_spec.rb +++ b/spec/models/body_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Body -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Body + # Please update as you see appropriate describe 'Body' do before do # run before each test - @instance = SwaggerClient::Body.new + @instance = AuthressSdk::Body.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Body' do it 'should create an instance of Body' do - expect(@instance).to be_instance_of(SwaggerClient::Body) + expect(@instance).to be_instance_of(AuthressSdk::Body) end end describe 'test attribute "account"' do diff --git a/spec/models/claim_request_spec.rb b/spec/models/claim_request_spec.rb index 140e4d5..bd3c009 100644 --- a/spec/models/claim_request_spec.rb +++ b/spec/models/claim_request_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ClaimRequest -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ClaimRequest + # Please update as you see appropriate describe 'ClaimRequest' do before do # run before each test - @instance = SwaggerClient::ClaimRequest.new + @instance = AuthressSdk::ClaimRequest.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ClaimRequest' do it 'should create an instance of ClaimRequest' do - expect(@instance).to be_instance_of(SwaggerClient::ClaimRequest) + expect(@instance).to be_instance_of(AuthressSdk::ClaimRequest) end end describe 'test attribute "collection_resource"' do diff --git a/spec/models/claim_response_spec.rb b/spec/models/claim_response_spec.rb index d7ac787..9e52d89 100644 --- a/spec/models/claim_response_spec.rb +++ b/spec/models/claim_response_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ClaimResponse -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ClaimResponse + # Please update as you see appropriate describe 'ClaimResponse' do before do # run before each test - @instance = SwaggerClient::ClaimResponse.new + @instance = AuthressSdk::ClaimResponse.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ClaimResponse' do it 'should create an instance of ClaimResponse' do - expect(@instance).to be_instance_of(SwaggerClient::ClaimResponse) + expect(@instance).to be_instance_of(AuthressSdk::ClaimResponse) end end end diff --git a/spec/models/client_access_key_spec.rb b/spec/models/client_access_key_spec.rb index 67549fa..4a70555 100644 --- a/spec/models/client_access_key_spec.rb +++ b/spec/models/client_access_key_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ClientAccessKey -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ClientAccessKey + # Please update as you see appropriate describe 'ClientAccessKey' do before do # run before each test - @instance = SwaggerClient::ClientAccessKey.new + @instance = AuthressSdk::ClientAccessKey.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ClientAccessKey' do it 'should create an instance of ClientAccessKey' do - expect(@instance).to be_instance_of(SwaggerClient::ClientAccessKey) + expect(@instance).to be_instance_of(AuthressSdk::ClientAccessKey) end end describe 'test attribute "key_id"' do diff --git a/spec/models/client_collection_clients_spec.rb b/spec/models/client_collection_clients_spec.rb index 3f92e33..06d3704 100644 --- a/spec/models/client_collection_clients_spec.rb +++ b/spec/models/client_collection_clients_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ClientCollectionClients -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ClientCollectionClients + # Please update as you see appropriate describe 'ClientCollectionClients' do before do # run before each test - @instance = SwaggerClient::ClientCollectionClients.new + @instance = AuthressSdk::ClientCollectionClients.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ClientCollectionClients' do it 'should create an instance of ClientCollectionClients' do - expect(@instance).to be_instance_of(SwaggerClient::ClientCollectionClients) + expect(@instance).to be_instance_of(AuthressSdk::ClientCollectionClients) end end describe 'test attribute "client_id"' do diff --git a/spec/models/client_collection_spec.rb b/spec/models/client_collection_spec.rb index b68dc30..6c30cdf 100644 --- a/spec/models/client_collection_spec.rb +++ b/spec/models/client_collection_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ClientCollection -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ClientCollection + # Please update as you see appropriate describe 'ClientCollection' do before do # run before each test - @instance = SwaggerClient::ClientCollection.new + @instance = AuthressSdk::ClientCollection.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ClientCollection' do it 'should create an instance of ClientCollection' do - expect(@instance).to be_instance_of(SwaggerClient::ClientCollection) + expect(@instance).to be_instance_of(AuthressSdk::ClientCollection) end end describe 'test attribute "clients"' do diff --git a/spec/models/client_spec.rb b/spec/models/client_spec.rb index b72236d..fb07c53 100644 --- a/spec/models/client_spec.rb +++ b/spec/models/client_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Client -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Client + # Please update as you see appropriate describe 'Client' do before do # run before each test - @instance = SwaggerClient::Client.new + @instance = AuthressSdk::Client.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Client' do it 'should create an instance of Client' do - expect(@instance).to be_instance_of(SwaggerClient::Client) + expect(@instance).to be_instance_of(AuthressSdk::Client) end end describe 'test attribute "client_id"' do diff --git a/spec/models/identity_collection_identities_spec.rb b/spec/models/identity_collection_identities_spec.rb index 418cbec..27af855 100644 --- a/spec/models/identity_collection_identities_spec.rb +++ b/spec/models/identity_collection_identities_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::IdentityCollectionIdentities -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::IdentityCollectionIdentities + # Please update as you see appropriate describe 'IdentityCollectionIdentities' do before do # run before each test - @instance = SwaggerClient::IdentityCollectionIdentities.new + @instance = AuthressSdk::IdentityCollectionIdentities.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of IdentityCollectionIdentities' do it 'should create an instance of IdentityCollectionIdentities' do - expect(@instance).to be_instance_of(SwaggerClient::IdentityCollectionIdentities) + expect(@instance).to be_instance_of(AuthressSdk::IdentityCollectionIdentities) end end describe 'test attribute "issuer"' do diff --git a/spec/models/identity_collection_spec.rb b/spec/models/identity_collection_spec.rb index 9811917..8d5d6b3 100644 --- a/spec/models/identity_collection_spec.rb +++ b/spec/models/identity_collection_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::IdentityCollection -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::IdentityCollection + # Please update as you see appropriate describe 'IdentityCollection' do before do # run before each test - @instance = SwaggerClient::IdentityCollection.new + @instance = AuthressSdk::IdentityCollection.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of IdentityCollection' do it 'should create an instance of IdentityCollection' do - expect(@instance).to be_instance_of(SwaggerClient::IdentityCollection) + expect(@instance).to be_instance_of(AuthressSdk::IdentityCollection) end end describe 'test attribute "identities"' do diff --git a/spec/models/identity_request_spec.rb b/spec/models/identity_request_spec.rb index 65198d5..fddda46 100644 --- a/spec/models/identity_request_spec.rb +++ b/spec/models/identity_request_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::IdentityRequest -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::IdentityRequest + # Please update as you see appropriate describe 'IdentityRequest' do before do # run before each test - @instance = SwaggerClient::IdentityRequest.new + @instance = AuthressSdk::IdentityRequest.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of IdentityRequest' do it 'should create an instance of IdentityRequest' do - expect(@instance).to be_instance_of(SwaggerClient::IdentityRequest) + expect(@instance).to be_instance_of(AuthressSdk::IdentityRequest) end end describe 'test attribute "jwt"' do diff --git a/spec/models/identity_spec.rb b/spec/models/identity_spec.rb index 4ba1696..4a54ab0 100644 --- a/spec/models/identity_spec.rb +++ b/spec/models/identity_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Identity -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Identity + # Please update as you see appropriate describe 'Identity' do before do # run before each test - @instance = SwaggerClient::Identity.new + @instance = AuthressSdk::Identity.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Identity' do it 'should create an instance of Identity' do - expect(@instance).to be_instance_of(SwaggerClient::Identity) + expect(@instance).to be_instance_of(AuthressSdk::Identity) end end describe 'test attribute "issuer"' do diff --git a/spec/models/inline_response_200_10_spec.rb b/spec/models/inline_response_200_10_spec.rb index 623a72a..e7b13a4 100644 --- a/spec/models/inline_response_200_10_spec.rb +++ b/spec/models/inline_response_200_10_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse20010 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse20010 + # Please update as you see appropriate describe 'InlineResponse20010' do before do # run before each test - @instance = SwaggerClient::InlineResponse20010.new + @instance = AuthressSdk::InlineResponse20010.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse20010' do it 'should create an instance of InlineResponse20010' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse20010) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse20010) end end describe 'test attribute "role_id"' do diff --git a/spec/models/inline_response_200_11_spec.rb b/spec/models/inline_response_200_11_spec.rb index 99c5b18..a72e213 100644 --- a/spec/models/inline_response_200_11_spec.rb +++ b/spec/models/inline_response_200_11_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse20011 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse20011 + # Please update as you see appropriate describe 'InlineResponse20011' do before do # run before each test - @instance = SwaggerClient::InlineResponse20011.new + @instance = AuthressSdk::InlineResponse20011.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse20011' do it 'should create an instance of InlineResponse20011' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse20011) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse20011) end end describe 'test attribute "accounts"' do diff --git a/spec/models/inline_response_200_12_spec.rb b/spec/models/inline_response_200_12_spec.rb index af9353e..619e425 100644 --- a/spec/models/inline_response_200_12_spec.rb +++ b/spec/models/inline_response_200_12_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse20012 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse20012 + # Please update as you see appropriate describe 'InlineResponse20012' do before do # run before each test - @instance = SwaggerClient::InlineResponse20012.new + @instance = AuthressSdk::InlineResponse20012.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse20012' do it 'should create an instance of InlineResponse20012' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse20012) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse20012) end end describe 'test attribute "identities"' do diff --git a/spec/models/inline_response_200_13_spec.rb b/spec/models/inline_response_200_13_spec.rb index 2efc871..dee4028 100644 --- a/spec/models/inline_response_200_13_spec.rb +++ b/spec/models/inline_response_200_13_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse20013 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse20013 + # Please update as you see appropriate describe 'InlineResponse20013' do before do # run before each test - @instance = SwaggerClient::InlineResponse20013.new + @instance = AuthressSdk::InlineResponse20013.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse20013' do it 'should create an instance of InlineResponse20013' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse20013) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse20013) end end describe 'test attribute "clients"' do diff --git a/spec/models/inline_response_200_14_spec.rb b/spec/models/inline_response_200_14_spec.rb index 3fb8743..1f40d89 100644 --- a/spec/models/inline_response_200_14_spec.rb +++ b/spec/models/inline_response_200_14_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse20014 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse20014 + # Please update as you see appropriate describe 'InlineResponse20014' do before do # run before each test - @instance = SwaggerClient::InlineResponse20014.new + @instance = AuthressSdk::InlineResponse20014.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse20014' do it 'should create an instance of InlineResponse20014' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse20014) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse20014) end end describe 'test attribute "client_id"' do diff --git a/spec/models/inline_response_200_15_spec.rb b/spec/models/inline_response_200_15_spec.rb index 91005b8..da309ff 100644 --- a/spec/models/inline_response_200_15_spec.rb +++ b/spec/models/inline_response_200_15_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse20015 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse20015 + # Please update as you see appropriate describe 'InlineResponse20015' do before do # run before each test - @instance = SwaggerClient::InlineResponse20015.new + @instance = AuthressSdk::InlineResponse20015.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse20015' do it 'should create an instance of InlineResponse20015' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse20015) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse20015) end end describe 'test attribute "key_id"' do diff --git a/spec/models/inline_response_200_1_spec.rb b/spec/models/inline_response_200_1_spec.rb index 0a03cef..d0d997c 100644 --- a/spec/models/inline_response_200_1_spec.rb +++ b/spec/models/inline_response_200_1_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2001 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2001 + # Please update as you see appropriate describe 'InlineResponse2001' do before do # run before each test - @instance = SwaggerClient::InlineResponse2001.new + @instance = AuthressSdk::InlineResponse2001.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2001' do it 'should create an instance of InlineResponse2001' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2001) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2001) end end describe 'test attribute "account"' do diff --git a/spec/models/inline_response_200_2_spec.rb b/spec/models/inline_response_200_2_spec.rb index f232eb4..0cda11e 100644 --- a/spec/models/inline_response_200_2_spec.rb +++ b/spec/models/inline_response_200_2_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2002 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2002 + # Please update as you see appropriate describe 'InlineResponse2002' do before do # run before each test - @instance = SwaggerClient::InlineResponse2002.new + @instance = AuthressSdk::InlineResponse2002.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2002' do it 'should create an instance of InlineResponse2002' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2002) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2002) end end describe 'test attribute "account"' do diff --git a/spec/models/inline_response_200_3_spec.rb b/spec/models/inline_response_200_3_spec.rb index d79d7a7..d37e806 100644 --- a/spec/models/inline_response_200_3_spec.rb +++ b/spec/models/inline_response_200_3_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2003 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2003 + # Please update as you see appropriate describe 'InlineResponse2003' do before do # run before each test - @instance = SwaggerClient::InlineResponse2003.new + @instance = AuthressSdk::InlineResponse2003.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2003' do it 'should create an instance of InlineResponse2003' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2003) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2003) end end describe 'test attribute "account"' do diff --git a/spec/models/inline_response_200_4_spec.rb b/spec/models/inline_response_200_4_spec.rb index ef553ac..2faa593 100644 --- a/spec/models/inline_response_200_4_spec.rb +++ b/spec/models/inline_response_200_4_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2004 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2004 + # Please update as you see appropriate describe 'InlineResponse2004' do before do # run before each test - @instance = SwaggerClient::InlineResponse2004.new + @instance = AuthressSdk::InlineResponse2004.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2004' do it 'should create an instance of InlineResponse2004' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2004) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2004) end end describe 'test attribute "resources"' do diff --git a/spec/models/inline_response_200_5_spec.rb b/spec/models/inline_response_200_5_spec.rb index ebee64d..e1c1d93 100644 --- a/spec/models/inline_response_200_5_spec.rb +++ b/spec/models/inline_response_200_5_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2005 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2005 + # Please update as you see appropriate describe 'InlineResponse2005' do before do # run before each test - @instance = SwaggerClient::InlineResponse2005.new + @instance = AuthressSdk::InlineResponse2005.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2005' do it 'should create an instance of InlineResponse2005' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2005) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2005) end end describe 'test attribute "permissions"' do diff --git a/spec/models/inline_response_200_6_spec.rb b/spec/models/inline_response_200_6_spec.rb index dd02cd5..85ecdf7 100644 --- a/spec/models/inline_response_200_6_spec.rb +++ b/spec/models/inline_response_200_6_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2006 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2006 + # Please update as you see appropriate describe 'InlineResponse2006' do before do # run before each test - @instance = SwaggerClient::InlineResponse2006.new + @instance = AuthressSdk::InlineResponse2006.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2006' do it 'should create an instance of InlineResponse2006' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2006) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2006) end end describe 'test attribute "users"' do diff --git a/spec/models/inline_response_200_7_spec.rb b/spec/models/inline_response_200_7_spec.rb index deabb6e..3fdd7bd 100644 --- a/spec/models/inline_response_200_7_spec.rb +++ b/spec/models/inline_response_200_7_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2007 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2007 + # Please update as you see appropriate describe 'InlineResponse2007' do before do # run before each test - @instance = SwaggerClient::InlineResponse2007.new + @instance = AuthressSdk::InlineResponse2007.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2007' do it 'should create an instance of InlineResponse2007' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2007) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2007) end end describe 'test attribute "records"' do diff --git a/spec/models/inline_response_200_8_spec.rb b/spec/models/inline_response_200_8_spec.rb index ad270bb..22a234f 100644 --- a/spec/models/inline_response_200_8_spec.rb +++ b/spec/models/inline_response_200_8_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2008 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2008 + # Please update as you see appropriate describe 'InlineResponse2008' do before do # run before each test - @instance = SwaggerClient::InlineResponse2008.new + @instance = AuthressSdk::InlineResponse2008.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2008' do it 'should create an instance of InlineResponse2008' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2008) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2008) end end describe 'test attribute "record_id"' do diff --git a/spec/models/inline_response_200_9_spec.rb b/spec/models/inline_response_200_9_spec.rb index 5b44fa7..9a29424 100644 --- a/spec/models/inline_response_200_9_spec.rb +++ b/spec/models/inline_response_200_9_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse2009 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse2009 + # Please update as you see appropriate describe 'InlineResponse2009' do before do # run before each test - @instance = SwaggerClient::InlineResponse2009.new + @instance = AuthressSdk::InlineResponse2009.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse2009' do it 'should create an instance of InlineResponse2009' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse2009) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse2009) end end describe 'test attribute "account_id"' do diff --git a/spec/models/inline_response_200_spec.rb b/spec/models/inline_response_200_spec.rb index 9a05696..88c147f 100644 --- a/spec/models/inline_response_200_spec.rb +++ b/spec/models/inline_response_200_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::InlineResponse200 -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::InlineResponse200 + # Please update as you see appropriate describe 'InlineResponse200' do before do # run before each test - @instance = SwaggerClient::InlineResponse200.new + @instance = AuthressSdk::InlineResponse200.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of InlineResponse200' do it 'should create an instance of InlineResponse200' do - expect(@instance).to be_instance_of(SwaggerClient::InlineResponse200) + expect(@instance).to be_instance_of(AuthressSdk::InlineResponse200) end end describe 'test attribute "account"' do diff --git a/spec/models/invite_spec.rb b/spec/models/invite_spec.rb index 981863a..a375530 100644 --- a/spec/models/invite_spec.rb +++ b/spec/models/invite_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Invite -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Invite + # Please update as you see appropriate describe 'Invite' do before do # run before each test - @instance = SwaggerClient::Invite.new + @instance = AuthressSdk::Invite.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Invite' do it 'should create an instance of Invite' do - expect(@instance).to be_instance_of(SwaggerClient::Invite) + expect(@instance).to be_instance_of(AuthressSdk::Invite) end end describe 'test attribute "email"' do diff --git a/spec/models/link_spec.rb b/spec/models/link_spec.rb index 054d119..f2f19ce 100644 --- a/spec/models/link_spec.rb +++ b/spec/models/link_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Link -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Link + # Please update as you see appropriate describe 'Link' do before do # run before each test - @instance = SwaggerClient::Link.new + @instance = AuthressSdk::Link.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Link' do it 'should create an instance of Link' do - expect(@instance).to be_instance_of(SwaggerClient::Link) + expect(@instance).to be_instance_of(AuthressSdk::Link) end end describe 'test attribute "href"' do diff --git a/spec/models/metadata_object_spec.rb b/spec/models/metadata_object_spec.rb index 5141ad1..7d5e741 100644 --- a/spec/models/metadata_object_spec.rb +++ b/spec/models/metadata_object_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::MetadataObject -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::MetadataObject + # Please update as you see appropriate describe 'MetadataObject' do before do # run before each test - @instance = SwaggerClient::MetadataObject.new + @instance = AuthressSdk::MetadataObject.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of MetadataObject' do it 'should create an instance of MetadataObject' do - expect(@instance).to be_instance_of(SwaggerClient::MetadataObject) + expect(@instance).to be_instance_of(AuthressSdk::MetadataObject) end end describe 'test attribute "account"' do diff --git a/spec/models/permission_object_spec.rb b/spec/models/permission_object_spec.rb index c3be5d6..d97ed6d 100644 --- a/spec/models/permission_object_spec.rb +++ b/spec/models/permission_object_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::PermissionObject -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::PermissionObject + # Please update as you see appropriate describe 'PermissionObject' do before do # run before each test - @instance = SwaggerClient::PermissionObject.new + @instance = AuthressSdk::PermissionObject.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of PermissionObject' do it 'should create an instance of PermissionObject' do - expect(@instance).to be_instance_of(SwaggerClient::PermissionObject) + expect(@instance).to be_instance_of(AuthressSdk::PermissionObject) end end describe 'test attribute "action"' do diff --git a/spec/models/permission_response_spec.rb b/spec/models/permission_response_spec.rb index 7ceff8f..8510d94 100644 --- a/spec/models/permission_response_spec.rb +++ b/spec/models/permission_response_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::PermissionResponse -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::PermissionResponse + # Please update as you see appropriate describe 'PermissionResponse' do before do # run before each test - @instance = SwaggerClient::PermissionResponse.new + @instance = AuthressSdk::PermissionResponse.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of PermissionResponse' do it 'should create an instance of PermissionResponse' do - expect(@instance).to be_instance_of(SwaggerClient::PermissionResponse) + expect(@instance).to be_instance_of(AuthressSdk::PermissionResponse) end end describe 'test attribute "account"' do diff --git a/spec/models/resource_permission_collection_links_next_spec.rb b/spec/models/resource_permission_collection_links_next_spec.rb index 75dcdcd..ce5b200 100644 --- a/spec/models/resource_permission_collection_links_next_spec.rb +++ b/spec/models/resource_permission_collection_links_next_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ResourcePermissionCollectionLinksNext -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ResourcePermissionCollectionLinksNext + # Please update as you see appropriate describe 'ResourcePermissionCollectionLinksNext' do before do # run before each test - @instance = SwaggerClient::ResourcePermissionCollectionLinksNext.new + @instance = AuthressSdk::ResourcePermissionCollectionLinksNext.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ResourcePermissionCollectionLinksNext' do it 'should create an instance of ResourcePermissionCollectionLinksNext' do - expect(@instance).to be_instance_of(SwaggerClient::ResourcePermissionCollectionLinksNext) + expect(@instance).to be_instance_of(AuthressSdk::ResourcePermissionCollectionLinksNext) end end describe 'test attribute "href"' do diff --git a/spec/models/resource_permission_collection_links_spec.rb b/spec/models/resource_permission_collection_links_spec.rb index b060aa1..4e24a54 100644 --- a/spec/models/resource_permission_collection_links_spec.rb +++ b/spec/models/resource_permission_collection_links_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ResourcePermissionCollectionLinks -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ResourcePermissionCollectionLinks + # Please update as you see appropriate describe 'ResourcePermissionCollectionLinks' do before do # run before each test - @instance = SwaggerClient::ResourcePermissionCollectionLinks.new + @instance = AuthressSdk::ResourcePermissionCollectionLinks.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ResourcePermissionCollectionLinks' do it 'should create an instance of ResourcePermissionCollectionLinks' do - expect(@instance).to be_instance_of(SwaggerClient::ResourcePermissionCollectionLinks) + expect(@instance).to be_instance_of(AuthressSdk::ResourcePermissionCollectionLinks) end end describe 'test attribute "_self"' do diff --git a/spec/models/resource_permission_collection_resources_spec.rb b/spec/models/resource_permission_collection_resources_spec.rb index 5b9ea74..99c06fc 100644 --- a/spec/models/resource_permission_collection_resources_spec.rb +++ b/spec/models/resource_permission_collection_resources_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ResourcePermissionCollectionResources -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ResourcePermissionCollectionResources + # Please update as you see appropriate describe 'ResourcePermissionCollectionResources' do before do # run before each test - @instance = SwaggerClient::ResourcePermissionCollectionResources.new + @instance = AuthressSdk::ResourcePermissionCollectionResources.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ResourcePermissionCollectionResources' do it 'should create an instance of ResourcePermissionCollectionResources' do - expect(@instance).to be_instance_of(SwaggerClient::ResourcePermissionCollectionResources) + expect(@instance).to be_instance_of(AuthressSdk::ResourcePermissionCollectionResources) end end describe 'test attribute "permissions"' do diff --git a/spec/models/resource_permission_collection_spec.rb b/spec/models/resource_permission_collection_spec.rb index 4c150a1..0c40953 100644 --- a/spec/models/resource_permission_collection_spec.rb +++ b/spec/models/resource_permission_collection_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ResourcePermissionCollection -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ResourcePermissionCollection + # Please update as you see appropriate describe 'ResourcePermissionCollection' do before do # run before each test - @instance = SwaggerClient::ResourcePermissionCollection.new + @instance = AuthressSdk::ResourcePermissionCollection.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ResourcePermissionCollection' do it 'should create an instance of ResourcePermissionCollection' do - expect(@instance).to be_instance_of(SwaggerClient::ResourcePermissionCollection) + expect(@instance).to be_instance_of(AuthressSdk::ResourcePermissionCollection) end end describe 'test attribute "resources"' do diff --git a/spec/models/resource_permission_spec.rb b/spec/models/resource_permission_spec.rb index e910c33..b77ea81 100644 --- a/spec/models/resource_permission_spec.rb +++ b/spec/models/resource_permission_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ResourcePermission -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ResourcePermission + # Please update as you see appropriate describe 'ResourcePermission' do before do # run before each test - @instance = SwaggerClient::ResourcePermission.new + @instance = AuthressSdk::ResourcePermission.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ResourcePermission' do it 'should create an instance of ResourcePermission' do - expect(@instance).to be_instance_of(SwaggerClient::ResourcePermission) + expect(@instance).to be_instance_of(AuthressSdk::ResourcePermission) end end describe 'test attribute "permissions"' do diff --git a/spec/models/resource_users_collection_spec.rb b/spec/models/resource_users_collection_spec.rb index f0bd6b4..7d45e03 100644 --- a/spec/models/resource_users_collection_spec.rb +++ b/spec/models/resource_users_collection_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::ResourceUsersCollection -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::ResourceUsersCollection + # Please update as you see appropriate describe 'ResourceUsersCollection' do before do # run before each test - @instance = SwaggerClient::ResourceUsersCollection.new + @instance = AuthressSdk::ResourceUsersCollection.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of ResourceUsersCollection' do it 'should create an instance of ResourceUsersCollection' do - expect(@instance).to be_instance_of(SwaggerClient::ResourceUsersCollection) + expect(@instance).to be_instance_of(AuthressSdk::ResourceUsersCollection) end end describe 'test attribute "users"' do diff --git a/spec/models/role_spec.rb b/spec/models/role_spec.rb index 656d130..6558e80 100644 --- a/spec/models/role_spec.rb +++ b/spec/models/role_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Role -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Role + # Please update as you see appropriate describe 'Role' do before do # run before each test - @instance = SwaggerClient::Role.new + @instance = AuthressSdk::Role.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Role' do it 'should create an instance of Role' do - expect(@instance).to be_instance_of(SwaggerClient::Role) + expect(@instance).to be_instance_of(AuthressSdk::Role) end end describe 'test attribute "role_id"' do diff --git a/spec/models/statement_spec.rb b/spec/models/statement_spec.rb index 8095c72..a9c6d15 100644 --- a/spec/models/statement_spec.rb +++ b/spec/models/statement_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::Statement -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::Statement + # Please update as you see appropriate describe 'Statement' do before do # run before each test - @instance = SwaggerClient::Statement.new + @instance = AuthressSdk::Statement.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of Statement' do it 'should create an instance of Statement' do - expect(@instance).to be_instance_of(SwaggerClient::Statement) + expect(@instance).to be_instance_of(AuthressSdk::Statement) end end describe 'test attribute "roles"' do diff --git a/spec/models/token_request_spec.rb b/spec/models/token_request_spec.rb index b63d64c..adec12d 100644 --- a/spec/models/token_request_spec.rb +++ b/spec/models/token_request_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::TokenRequest -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::TokenRequest + # Please update as you see appropriate describe 'TokenRequest' do before do # run before each test - @instance = SwaggerClient::TokenRequest.new + @instance = AuthressSdk::TokenRequest.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of TokenRequest' do it 'should create an instance of TokenRequest' do - expect(@instance).to be_instance_of(SwaggerClient::TokenRequest) + expect(@instance).to be_instance_of(AuthressSdk::TokenRequest) end end describe 'test attribute "statements"' do diff --git a/spec/models/user_resources_resources_spec.rb b/spec/models/user_resources_resources_spec.rb index 06b2703..474168e 100644 --- a/spec/models/user_resources_resources_spec.rb +++ b/spec/models/user_resources_resources_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::UserResourcesResources -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::UserResourcesResources + # Please update as you see appropriate describe 'UserResourcesResources' do before do # run before each test - @instance = SwaggerClient::UserResourcesResources.new + @instance = AuthressSdk::UserResourcesResources.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of UserResourcesResources' do it 'should create an instance of UserResourcesResources' do - expect(@instance).to be_instance_of(SwaggerClient::UserResourcesResources) + expect(@instance).to be_instance_of(AuthressSdk::UserResourcesResources) end end describe 'test attribute "resource_uri"' do diff --git a/spec/models/user_resources_spec.rb b/spec/models/user_resources_spec.rb index e05e735..f3c1bb1 100644 --- a/spec/models/user_resources_spec.rb +++ b/spec/models/user_resources_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::UserResources -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::UserResources + # Please update as you see appropriate describe 'UserResources' do before do # run before each test - @instance = SwaggerClient::UserResources.new + @instance = AuthressSdk::UserResources.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of UserResources' do it 'should create an instance of UserResources' do - expect(@instance).to be_instance_of(SwaggerClient::UserResources) + expect(@instance).to be_instance_of(AuthressSdk::UserResources) end end describe 'test attribute "account"' do diff --git a/spec/models/user_spec.rb b/spec/models/user_spec.rb index 7e646ee..31efed6 100644 --- a/spec/models/user_spec.rb +++ b/spec/models/user_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::User -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::User + # Please update as you see appropriate describe 'User' do before do # run before each test - @instance = SwaggerClient::User.new + @instance = AuthressSdk::User.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of User' do it 'should create an instance of User' do - expect(@instance).to be_instance_of(SwaggerClient::User) + expect(@instance).to be_instance_of(AuthressSdk::User) end end describe 'test attribute "user_id"' do diff --git a/spec/models/user_token_links_self_spec.rb b/spec/models/user_token_links_self_spec.rb index 4a1469a..d00925b 100644 --- a/spec/models/user_token_links_self_spec.rb +++ b/spec/models/user_token_links_self_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::UserTokenLinksSelf -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::UserTokenLinksSelf + # Please update as you see appropriate describe 'UserTokenLinksSelf' do before do # run before each test - @instance = SwaggerClient::UserTokenLinksSelf.new + @instance = AuthressSdk::UserTokenLinksSelf.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of UserTokenLinksSelf' do it 'should create an instance of UserTokenLinksSelf' do - expect(@instance).to be_instance_of(SwaggerClient::UserTokenLinksSelf) + expect(@instance).to be_instance_of(AuthressSdk::UserTokenLinksSelf) end end describe 'test attribute "href"' do diff --git a/spec/models/user_token_links_spec.rb b/spec/models/user_token_links_spec.rb index 0eb3007..4ee52ce 100644 --- a/spec/models/user_token_links_spec.rb +++ b/spec/models/user_token_links_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::UserTokenLinks -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::UserTokenLinks + # Please update as you see appropriate describe 'UserTokenLinks' do before do # run before each test - @instance = SwaggerClient::UserTokenLinks.new + @instance = AuthressSdk::UserTokenLinks.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of UserTokenLinks' do it 'should create an instance of UserTokenLinks' do - expect(@instance).to be_instance_of(SwaggerClient::UserTokenLinks) + expect(@instance).to be_instance_of(AuthressSdk::UserTokenLinks) end end describe 'test attribute "_self"' do diff --git a/spec/models/user_token_spec.rb b/spec/models/user_token_spec.rb index 7ba8e45..dc15a77 100644 --- a/spec/models/user_token_spec.rb +++ b/spec/models/user_token_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::UserToken -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::UserToken + # Please update as you see appropriate describe 'UserToken' do before do # run before each test - @instance = SwaggerClient::UserToken.new + @instance = AuthressSdk::UserToken.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of UserToken' do it 'should create an instance of UserToken' do - expect(@instance).to be_instance_of(SwaggerClient::UserToken) + expect(@instance).to be_instance_of(AuthressSdk::UserToken) end end describe 'test attribute "account"' do diff --git a/spec/models/v1clients_options_spec.rb b/spec/models/v1clients_options_spec.rb index 02131dc..15e50a8 100644 --- a/spec/models/v1clients_options_spec.rb +++ b/spec/models/v1clients_options_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1clientsOptions -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1clientsOptions + # Please update as you see appropriate describe 'V1clientsOptions' do before do # run before each test - @instance = SwaggerClient::V1clientsOptions.new + @instance = AuthressSdk::V1clientsOptions.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1clientsOptions' do it 'should create an instance of V1clientsOptions' do - expect(@instance).to be_instance_of(SwaggerClient::V1clientsOptions) + expect(@instance).to be_instance_of(AuthressSdk::V1clientsOptions) end end describe 'test attribute "grant_user_permissions_access"' do diff --git a/spec/models/v1records_account_spec.rb b/spec/models/v1records_account_spec.rb index 81fd33c..897ba8f 100644 --- a/spec/models/v1records_account_spec.rb +++ b/spec/models/v1records_account_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1recordsAccount -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1recordsAccount + # Please update as you see appropriate describe 'V1recordsAccount' do before do # run before each test - @instance = SwaggerClient::V1recordsAccount.new + @instance = AuthressSdk::V1recordsAccount.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1recordsAccount' do it 'should create an instance of V1recordsAccount' do - expect(@instance).to be_instance_of(SwaggerClient::V1recordsAccount) + expect(@instance).to be_instance_of(AuthressSdk::V1recordsAccount) end end describe 'test attribute "account_id"' do diff --git a/spec/models/v1records_links_self_spec.rb b/spec/models/v1records_links_self_spec.rb index dcf2d3c..911a0d6 100644 --- a/spec/models/v1records_links_self_spec.rb +++ b/spec/models/v1records_links_self_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1recordsLinksSelf -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1recordsLinksSelf + # Please update as you see appropriate describe 'V1recordsLinksSelf' do before do # run before each test - @instance = SwaggerClient::V1recordsLinksSelf.new + @instance = AuthressSdk::V1recordsLinksSelf.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1recordsLinksSelf' do it 'should create an instance of V1recordsLinksSelf' do - expect(@instance).to be_instance_of(SwaggerClient::V1recordsLinksSelf) + expect(@instance).to be_instance_of(AuthressSdk::V1recordsLinksSelf) end end describe 'test attribute "href"' do diff --git a/spec/models/v1records_links_spec.rb b/spec/models/v1records_links_spec.rb index 1d914ee..1499e53 100644 --- a/spec/models/v1records_links_spec.rb +++ b/spec/models/v1records_links_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1recordsLinks -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1recordsLinks + # Please update as you see appropriate describe 'V1recordsLinks' do before do # run before each test - @instance = SwaggerClient::V1recordsLinks.new + @instance = AuthressSdk::V1recordsLinks.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1recordsLinks' do it 'should create an instance of V1recordsLinks' do - expect(@instance).to be_instance_of(SwaggerClient::V1recordsLinks) + expect(@instance).to be_instance_of(AuthressSdk::V1recordsLinks) end end describe 'test attribute "_self"' do diff --git a/spec/models/v1records_users_spec.rb b/spec/models/v1records_users_spec.rb index e224b28..4be0e4b 100644 --- a/spec/models/v1records_users_spec.rb +++ b/spec/models/v1records_users_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1recordsUsers -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1recordsUsers + # Please update as you see appropriate describe 'V1recordsUsers' do before do # run before each test - @instance = SwaggerClient::V1recordsUsers.new + @instance = AuthressSdk::V1recordsUsers.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1recordsUsers' do it 'should create an instance of V1recordsUsers' do - expect(@instance).to be_instance_of(SwaggerClient::V1recordsUsers) + expect(@instance).to be_instance_of(AuthressSdk::V1recordsUsers) end end describe 'test attribute "user_id"' do diff --git a/spec/models/v1resourcesresource_uri_permissions_spec.rb b/spec/models/v1resourcesresource_uri_permissions_spec.rb index c695266..b8a5bc9 100644 --- a/spec/models/v1resourcesresource_uri_permissions_spec.rb +++ b/spec/models/v1resourcesresource_uri_permissions_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1resourcesresourceUriPermissions -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1resourcesresourceUriPermissions + # Please update as you see appropriate describe 'V1resourcesresourceUriPermissions' do before do # run before each test - @instance = SwaggerClient::V1resourcesresourceUriPermissions.new + @instance = AuthressSdk::V1resourcesresourceUriPermissions.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1resourcesresourceUriPermissions' do it 'should create an instance of V1resourcesresourceUriPermissions' do - expect(@instance).to be_instance_of(SwaggerClient::V1resourcesresourceUriPermissions) + expect(@instance).to be_instance_of(AuthressSdk::V1resourcesresourceUriPermissions) end end describe 'test attribute "action"' do diff --git a/spec/models/v1roles_permissions_spec.rb b/spec/models/v1roles_permissions_spec.rb index eb27e41..76b1a62 100644 --- a/spec/models/v1roles_permissions_spec.rb +++ b/spec/models/v1roles_permissions_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1rolesPermissions -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1rolesPermissions + # Please update as you see appropriate describe 'V1rolesPermissions' do before do # run before each test - @instance = SwaggerClient::V1rolesPermissions.new + @instance = AuthressSdk::V1rolesPermissions.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1rolesPermissions' do it 'should create an instance of V1rolesPermissions' do - expect(@instance).to be_instance_of(SwaggerClient::V1rolesPermissions) + expect(@instance).to be_instance_of(AuthressSdk::V1rolesPermissions) end end describe 'test attribute "action"' do diff --git a/spec/models/v1usersuser_idresourcesresource_urimetadata_account_spec.rb b/spec/models/v1usersuser_idresourcesresource_urimetadata_account_spec.rb index 8dfd816..4ecf679 100644 --- a/spec/models/v1usersuser_idresourcesresource_urimetadata_account_spec.rb +++ b/spec/models/v1usersuser_idresourcesresource_urimetadata_account_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1usersuserIdresourcesresourceUrimetadataAccount -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1usersuserIdresourcesresourceUrimetadataAccount + # Please update as you see appropriate describe 'V1usersuserIdresourcesresourceUrimetadataAccount' do before do # run before each test - @instance = SwaggerClient::V1usersuserIdresourcesresourceUrimetadataAccount.new + @instance = AuthressSdk::V1usersuserIdresourcesresourceUrimetadataAccount.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1usersuserIdresourcesresourceUrimetadataAccount' do it 'should create an instance of V1usersuserIdresourcesresourceUrimetadataAccount' do - expect(@instance).to be_instance_of(SwaggerClient::V1usersuserIdresourcesresourceUrimetadataAccount) + expect(@instance).to be_instance_of(AuthressSdk::V1usersuserIdresourcesresourceUrimetadataAccount) end end describe 'test attribute "account_id"' do diff --git a/spec/models/v1usersuser_idtokens_resources_spec.rb b/spec/models/v1usersuser_idtokens_resources_spec.rb index 772c87f..41ebff5 100644 --- a/spec/models/v1usersuser_idtokens_resources_spec.rb +++ b/spec/models/v1usersuser_idtokens_resources_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1usersuserIdtokensResources -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1usersuserIdtokensResources + # Please update as you see appropriate describe 'V1usersuserIdtokensResources' do before do # run before each test - @instance = SwaggerClient::V1usersuserIdtokensResources.new + @instance = AuthressSdk::V1usersuserIdtokensResources.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1usersuserIdtokensResources' do it 'should create an instance of V1usersuserIdtokensResources' do - expect(@instance).to be_instance_of(SwaggerClient::V1usersuserIdtokensResources) + expect(@instance).to be_instance_of(AuthressSdk::V1usersuserIdtokensResources) end end describe 'test attribute "resource_uri"' do diff --git a/spec/models/v1usersuser_idtokens_statements_spec.rb b/spec/models/v1usersuser_idtokens_statements_spec.rb index 4d8ba51..cc83678 100644 --- a/spec/models/v1usersuser_idtokens_statements_spec.rb +++ b/spec/models/v1usersuser_idtokens_statements_spec.rb @@ -1,25 +1,18 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end require 'spec_helper' require 'json' require 'date' -# Unit tests for SwaggerClient::V1usersuserIdtokensStatements -# Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) +# Unit tests for AuthressSdk::V1usersuserIdtokensStatements + # Please update as you see appropriate describe 'V1usersuserIdtokensStatements' do before do # run before each test - @instance = SwaggerClient::V1usersuserIdtokensStatements.new + @instance = AuthressSdk::V1usersuserIdtokensStatements.new end after do @@ -28,7 +21,7 @@ describe 'test an instance of V1usersuserIdtokensStatements' do it 'should create an instance of V1usersuserIdtokensStatements' do - expect(@instance).to be_instance_of(SwaggerClient::V1usersuserIdtokensStatements) + expect(@instance).to be_instance_of(AuthressSdk::V1usersuserIdtokensStatements) end end describe 'test attribute "roles"' do diff --git a/spec/service_client_token_provider_spec.rb b/spec/service_client_token_provider_spec.rb new file mode 100644 index 0000000..98db1eb --- /dev/null +++ b/spec/service_client_token_provider_spec.rb @@ -0,0 +1,16 @@ +=begin + +=end + +require 'spec_helper' + +describe AuthressSdk::ServiceClientTokenProvider do + describe 'tokenProvider()' do + it "Generates service client access token" do + access_token = 'test-access-token' + tokenProvider = AuthressSdk::ServiceClientTokenProvider.new(access_token) + result = tokenProvider.get_token() + expect(result).to eq(access_token); + end + end +end diff --git a/spec/spec_helper.rb b/spec/spec_helper.rb index 2ed5a56..61b4402 100644 --- a/spec/spec_helper.rb +++ b/spec/spec_helper.rb @@ -1,16 +1,9 @@ =begin -#Authress -#

Authorization

Authorization for Authress is handled one of two different ways. Both mechanisms use oauth2 Bearer tokens.


Identity Provider JWT

Hook up your preferred identity provider directly to Authress. Authress will verify JWTs sourced from that identify provider and allow direct integration with these APIs. Any OIDC JWT provider works, Google, Auth0, Okta, etc... With this mechanism your web app can make direct calls to the permissions API on behalf of your users.
Link identity provider


Authress Clients

Regardless of using direct identity provider integration, with the API you can create Authress clients which can call any of the methods on the API. Your users won't be able to directly make API calls, all web app integrations must go through a service which stores the Authress private key.
Create Authress service client


Usage

Billable APIs

Most of the api available is completely free. Use it to populate your roles and configure your account. You'll only be charged for the ones marked as Billable.

  • Billable - These APIs count as calls for your account and will be charged.
  • Free - These are totally free.
  • Condition - Are conditionally free, see api methods for details.


API Access

Access to the following APIs is based on Authress permissions, not the application permissions assigned in Authress to the application services. Each resource is tagged with the required permission Action: Resource

- -OpenAPI spec version: v1 -Contact: support@authress.io -Generated by: https://github.com/swagger-api/swagger-codegen.git -Swagger Codegen version: 3.0.23 =end # load the gem -require 'swagger_client' +require 'authress_sdk' # The following was generated by the `rspec --init` command. Conventionally, all # specs live under a `spec` directory, which RSpec adds to the `$LOAD_PATH`.