Download JAR files tagged by oauth with all dependencies
kafka-oauth-client from group io.strimzi (version 0.15.0)
0 downloads
Artifact kafka-oauth-client
Group io.strimzi
Version 0.15.0
Last update 01. March 2024
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies kafka-oauth-common,
There are maybe transitive dependencies!
Group io.strimzi
Version 0.15.0
Last update 01. March 2024
Organization not specified
URL Not specified
License not specified
Dependencies amount 1
Dependencies kafka-oauth-common,
There are maybe transitive dependencies!
java-sdk from group software.reloadly (version 1.0.2)
The Reloadly SDK for Java provides Java APIs
for building software, integrating Reloadly's cost-effective, scalable, and reliable
products and APIs. The Reloadly Java SDK allows developers to code
against APIs for all of Reloadly's web services (Airtime, OAuth, Voucher, Gifting, Data, Bundles, etc.).
Group: software.reloadly Artifact: java-sdk
Show all versions
Show all versions
There is no JAR file uploaded. A download is not possible! Please choose another version.
0 downloads
Artifact java-sdk
Group software.reloadly
Version 1.0.2
Last update 07. January 2022
Organization not specified
URL https://github.com/reloadly/reloadly-sdk-java
License MIT License
Dependencies amount 8
Dependencies okhttp, logging-interceptor, commons-codec, jackson-databind, gson, lombok, maven-model, annotations,
There are maybe transitive dependencies!
Group software.reloadly
Version 1.0.2
Last update 07. January 2022
Organization not specified
URL https://github.com/reloadly/reloadly-sdk-java
License MIT License
Dependencies amount 8
Dependencies okhttp, logging-interceptor, commons-codec, jackson-databind, gson, lombok, maven-model, annotations,
There are maybe transitive dependencies!
stormpath-sdk-oauth from group com.stormpath.sdk (version 2.0.4-okta)
The Stormpath Java OAUTH HTTP implementation .jar is used at runtime.. This
implementation jar should be a runtime dependency only and should NOT be depended on at compile time by
your code. The implementations within this jar can change at any time without warning - use it with runtime
scope only.
Group: com.stormpath.sdk Artifact: stormpath-sdk-oauth
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact stormpath-sdk-oauth
Group com.stormpath.sdk
Version 2.0.4-okta
Last update 28. September 2017
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies stormpath-sdk-impl, org.apache.oltu.oauth2.authzserver, org.apache.oltu.oauth2.resourceserver, jcl-over-slf4j,
There are maybe transitive dependencies!
Group com.stormpath.sdk
Version 2.0.4-okta
Last update 28. September 2017
Organization not specified
URL Not specified
License not specified
Dependencies amount 4
Dependencies stormpath-sdk-impl, org.apache.oltu.oauth2.authzserver, org.apache.oltu.oauth2.resourceserver, jcl-over-slf4j,
There are maybe transitive dependencies!
dropbox-java-sdk from group com.syncthemall (version 1.5.3.2)
The Dropbox API for Java is a Dropbox supported client library for accessing the
JSON+REST interface to Dropbox. It supports OAuth proxied authentication. It is
designed to be simple and easy to use, as well as instructional in case you want
to write your own. It is MIT licensed.
0 downloads
Artifact dropbox-java-sdk
Group com.syncthemall
Version 1.5.3.2
Last update 15. April 2013
Organization Dropbox Inc.
URL http://www.dropbox.com/developers/
License MIT
Dependencies amount 4
Dependencies httpclient, httpmime, commons-logging, json-simple,
There are maybe transitive dependencies!
Group com.syncthemall
Version 1.5.3.2
Last update 15. April 2013
Organization Dropbox Inc.
URL http://www.dropbox.com/developers/
License MIT
Dependencies amount 4
Dependencies httpclient, httpmime, commons-logging, json-simple,
There are maybe transitive dependencies!
dropbox-client from group org.syncloud (version 1.5.3)
The Dropbox API for Java is a Dropbox supported client library for accessing the
JSON+REST interface to Dropbox. It supports OAuth proxied authentication. It is
designed to be simple and easy to use, as well as instructional in case you want
to write your own. It is MIT licensed.
Artifact dropbox-client
Group org.syncloud
Version 1.5.3
Last update 08. January 2013
Organization Dropbox Inc.
URL http://www.dropbox.com/developers/
License MIT
Dependencies amount 4
Dependencies httpclient, httpmime, commons-codec, json-simple,
There are maybe transitive dependencies!
Group org.syncloud
Version 1.5.3
Last update 08. January 2013
Organization Dropbox Inc.
URL http://www.dropbox.com/developers/
License MIT
Dependencies amount 4
Dependencies httpclient, httpmime, commons-codec, json-simple,
There are maybe transitive dependencies!
personify-scim-server from group be.personify.iam (version 2.1.2.RELEASE)
implementation for the scim v2 protocol in java supporting :
- create, get, put, delete, search, patch ( with attributes and excludedAttributes )
- bulk with circular reference processing, maxOperations and maxPayloadSize
- paging
- filtering
- discovery
- schema validation
- uniqueness constraint validation
- authentication : basic and OAUTH bearer token ( with roles )
- bearer token endpoint created and verified with Forgerock IDM SCIM connector (compatible)
- /ME endpoint
- auditing via KAFKA
Group: be.personify.iam Artifact: personify-scim-server
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact personify-scim-server
Group be.personify.iam
Version 2.1.2.RELEASE
Last update 24. August 2023
Organization personify
URL https://www.personify.be
License MIT
Dependencies amount 12
Dependencies spring-boot-starter-web, spring-boot-starter-aop, spring-data-rest-webmvc, spring-boot-starter-log4j2, spring-security-crypto, mongo-java-driver, personify-provisioning, personify-audit, postgresql, mysql-connector-java, orientdb-core, java-client,
There are maybe transitive dependencies!
Group be.personify.iam
Version 2.1.2.RELEASE
Last update 24. August 2023
Organization personify
URL https://www.personify.be
License MIT
Dependencies amount 12
Dependencies spring-boot-starter-web, spring-boot-starter-aop, spring-data-rest-webmvc, spring-boot-starter-log4j2, spring-security-crypto, mongo-java-driver, personify-provisioning, personify-audit, postgresql, mysql-connector-java, orientdb-core, java-client,
There are maybe transitive dependencies!
card-management-sdk from group io.sdks (version 1.1.0)
The Shell Card Management API is REST-based and employs OAUTH 2.0,Basic and ApiKey authentication. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes.
All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources. The internal workings of the platform are not important when interacting with the API. However, it is worth noting that the platform uses a microservice architecture to communicate with various backend systems and some API calls are processed asynchronously. All endpoints use the POST verb for retrieving, updating, creating and deleting resources in the Shell Card Platform. The endpoints that retrieve resources from the Shell Card Platform allow flexible search parameters in the API request body.
0 downloads
Artifact card-management-sdk
Group io.sdks
Version 1.1.0
Last update 02. July 2024
Organization not specified
URL https://www.shell.com/
License MIT License
Dependencies amount 3
Dependencies core-interfaces, core, okhttp-client-adapter,
There are maybe transitive dependencies!
Group io.sdks
Version 1.1.0
Last update 02. July 2024
Organization not specified
URL https://www.shell.com/
License MIT License
Dependencies amount 3
Dependencies core-interfaces, core, okhttp-client-adapter,
There are maybe transitive dependencies!
data-and-reporting-sdk from group io.sdks (version 1.0.0)
Data And Reporting product consists of API's which provides details of transaction and invoice informations about shell cards. The Shell Card Transaction and Invoice API is REST-based and employs Basic authentication in Version 1 and Oauth authentication in Version 2 end points. The API endpoints accept JSON-encoded request bodies, return JSON-encoded responses and use standard HTTP response codes. All resources are located in the Shell Card Platform. The Shell Card Platform is the overall platform that encompasses all the internal Shell systems used to manage resources.
Artifact data-and-reporting-sdk
Group io.sdks
Version 1.0.0
Last update 28. May 2024
Organization not specified
URL https://www.shell.com/
License MIT License
Dependencies amount 3
Dependencies core-interfaces, core, okhttp-client-adapter,
There are maybe transitive dependencies!
Group io.sdks
Version 1.0.0
Last update 28. May 2024
Organization not specified
URL https://www.shell.com/
License MIT License
Dependencies amount 3
Dependencies core-interfaces, core, okhttp-client-adapter,
There are maybe transitive dependencies!
tagmycode-netbeans from group com.tagmycode (version 2.3.0)
Provides the support for <a href="https://tagmycode.com">TagMyCode</a>.
This plugin allows you to manage your own snippets.<br/>
<br/>
Features:<br/>
* Add snippets: you can save your code snippets including description, language, and tags<br/>
* List snippets (CRUD): snippets are stored locally and you can filter, sort, create, modify, edit or delete them directly from the IDE<br/>
* Quick search: you can search your snippets and insert them directly into the document<br/>
<br/>
CHANGELOG:<br/>
<br/>
2.3.0 (released 2020-07-26)<br/>
* published plugin into Apache NetBeans Plugin Portal<br/>
* filter snippets by languages<br/>
<br/>
2.2.1 (released 2018-01-10)<br/>
* Quick Search dialog is now resizable</br>
* fixed syntax highlight for PHP and HTML</br>
* if refresh token is not valid user will be automatically logged out</br>
</br>
2.2.0 (released 2017-11-06)<br/>
* snippets management works in offline mode<br/>
* autodetect language on new snippet<br/>
* added settings dialog with editor theme and font size option<br/>
* added title and description to snippet view<br/>
* changed open browser class<br/>
* text can be dragged into table to create a new snippet<br/>
* snippets can be dragged directly into editor and the code are copied<br/>
* added "save as file" feature<br/>
* added "clone snippet" feature<br/>
* added "snippet properties" dialog<br/>
* detect binary file<br/>
<br/>
2.1.0 (released 2017-04-24)<br/>
* moved error messages from dialog to Netbeans Notification Log<br/>
* added welcome panel<br/>
* about dialog shows plugin version and framework version<br/>
* moved storage from JSON to SQL<br/>
<br/>
2.0 (released 2016-07-11)<br/>
* new user interface<br/>
* list of snippets stored locally<br/>
* syntax highlight powered by <a href="http://bobbylight.github.io/RSyntaxTextArea/">RSyntaxTextArea</a><br/>
* snippets are synchronized with server<br/>
* filter snippets<br/>
* quick search feature<br/>
* insert selected snippet at cursor in document<br/>
<br/>
1.1.3 (released 2015-12-18)<br/>
* Fix for NetBeans 8.1<br/>
<br/>
1.1.2 (released 2014-10-03)<br/>
* Switched authentication from OAuth 1.0a to OAuth 2<br/>
* Console write also snippet title when new snippet is created (thanks to bejoy)<br/>
<br/>
1.1 (released 2014-08-19)<br/>
* Added "Search snippets" feature<br/>
* Fixed some minor bugs<br/>
<br/>
1.0 (released 2014-04-14)<br/>
* First release with feature "Create snippet"<br/>
Artifact tagmycode-netbeans
Group com.tagmycode
Version 2.3.0
Last update 06. September 2020
Organization not specified
URL https://tagmycode.com
License Apache License 2.0
Dependencies amount 18
Dependencies commons-lang3, rsyntaxtextarea, guava, org-netbeans-api-annotations-common, org-openide-awt, org-netbeans-modules-settings, org-openide-dialogs, org-netbeans-modules-editor, org-netbeans-modules-keyring, org-openide-nodes, org-openide-util, org-openide-loaders, org-openide-windows, org-openide-util-ui, org-openide-text, org-netbeans-api-progress, log4j, tagmycode-plugin-framework,
There are maybe transitive dependencies!
Group com.tagmycode
Version 2.3.0
Last update 06. September 2020
Organization not specified
URL https://tagmycode.com
License Apache License 2.0
Dependencies amount 18
Dependencies commons-lang3, rsyntaxtextarea, guava, org-netbeans-api-annotations-common, org-openide-awt, org-netbeans-modules-settings, org-openide-dialogs, org-netbeans-modules-editor, org-netbeans-modules-keyring, org-openide-nodes, org-openide-util, org-openide-loaders, org-openide-windows, org-openide-util-ui, org-openide-text, org-netbeans-api-progress, log4j, tagmycode-plugin-framework,
There are maybe transitive dependencies!
pact-jvm-provider-lein_2.12 from group au.com.dius (version 3.6.15)
# Leiningen plugin to verify a provider [version 2.2.14+, 3.0.3+]
Leiningen plugin for verifying pacts against a provider. The plugin provides a `pact-verify` task which will verify all
configured pacts against your provider.
## To Use It
### 1. Add the plugin to your project plugins, preferably in it's own profile.
```clojure
:profiles {
:pact {
:plugins [[au.com.dius/pact-jvm-provider-lein_2.11 "3.2.11" :exclusions [commons-logging]]]
:dependencies [[ch.qos.logback/logback-core "1.1.3"]
[ch.qos.logback/logback-classic "1.1.3"]
[org.apache.httpcomponents/httpclient "4.4.1"]]
}}}
```
### 2. Define the pacts between your consumers and providers
You define all the providers and consumers within the `:pact` configuration element of your project.
```clojure
:pact {
:service-providers {
; You can define as many as you need, but each must have a unique name
:provider1 {
; All the provider properties are optional, and have sensible defaults (shown below)
:protocol "http"
:host "localhost"
:port 8080
:path "/"
:has-pact-with {
; Again, you can define as many consumers for each provider as you need, but each must have a unique name
:consumer1 {
; pact file can be either a path or an URL
:pact-file "path/to/provider1-consumer1-pact.json"
}
}
}
}
}
```
### 3. Execute `lein with-profile pact pact-verify`
You will have to have your provider running for this to pass.
## Enabling insecure SSL
For providers that are running on SSL with self-signed certificates, you need to enable insecure SSL mode by setting
`:insecure true` on the provider.
```clojure
:pact {
:service-providers {
:provider1 {
:protocol "https"
:host "localhost"
:port 8443
:insecure true
:has-pact-with {
:consumer1 {
:pact-file "path/to/provider1-consumer1-pact.json"
}
}
}
}
}
```
## Specifying a custom trust store
For environments that are running their own certificate chains:
```clojure
:pact {
:service-providers {
:provider1 {
:protocol "https"
:host "localhost"
:port 8443
:trust-store "relative/path/to/trustStore.jks"
:trust-store-password "changeme"
:has-pact-with {
:consumer1 {
:pact-file "path/to/provider1-consumer1-pact.json"
}
}
}
}
}
```
`:trust-store` is relative to the current working (build) directory. `:trust-store-password` defaults to `changeit`.
NOTE: The hostname will still be verified against the certificate.
## Modifying the requests before they are sent
Sometimes you may need to add things to the requests that can't be persisted in a pact file. Examples of these would
be authentication tokens, which have a small life span. The Leiningen plugin provides a request filter that can be
set to an anonymous function on the provider that will be called before the request is made. This function will receive the HttpRequest
object as a parameter.
```clojure
:pact {
:service-providers {
:provider1 {
; function that adds an Authorization header to each request
:request-filter #(.addHeader % "Authorization" "oauth-token eyJhbGciOiJSUzI1NiIsIm...")
:has-pact-with {
:consumer1 {
:pact-file "path/to/provider1-consumer1-pact.json"
}
}
}
}
}
```
__*Important Note:*__ You should only use this feature for things that can not be persisted in the pact file. By modifying
the request, you are potentially modifying the contract from the consumer tests!
## Modifying the HTTP Client Used
The default HTTP client is used for all requests to providers (created with a call to `HttpClients.createDefault()`).
This can be changed by specifying a function assigned to `:create-client` on the provider that returns a `CloseableHttpClient`.
The function will receive the provider info as a parameter.
## Turning off URL decoding of the paths in the pact file [version 3.3.3+]
By default the paths loaded from the pact file will be decoded before the request is sent to the provider. To turn this
behaviour off, set the system property `pact.verifier.disableUrlPathDecoding` to `true`.
__*Important Note:*__ If you turn off the url path decoding, you need to ensure that the paths in the pact files are
correctly encoded. The verifier will not be able to make a request with an invalid encoded path.
## Plugin Properties
The following plugin options can be specified on the command line:
|Property|Description|
|--------|-----------|
|:pact.showStacktrace|This turns on stacktrace printing for each request. It can help with diagnosing network errors|
|:pact.showFullDiff|This turns on displaying the full diff of the expected versus actual bodies [version 3.3.6+]|
|:pact.filter.consumers|Comma seperated list of consumer names to verify|
|:pact.filter.description|Only verify interactions whose description match the provided regular expression|
|:pact.filter.providerState|Only verify interactions whose provider state match the provided regular expression. An empty string matches interactions that have no state|
|:pact.verifier.publishResults|Publishing of verification results will be skipped unless this property is set to 'true' [version 3.5.18+]|
|:pact.matching.wildcard|Enables matching of map values ignoring the keys when this property is set to 'true'|
Example, to run verification only for a particular consumer:
```
$ lein with-profile pact pact-verify :pact.filter.consumers=:consumer2
```
## Provider States
For each provider you can specify a state change URL to use to switch the state of the provider. This URL will
receive the `providerState` description from the pact file before each interaction via a POST. The `:state-change-uses-body`
controls if the state is passed in the request body or as a query parameter.
These values can be set at the provider level, or for a specific consumer. Consumer values take precedent if both are given.
```clojure
:pact {
:service-providers {
:provider1 {
:state-change-url "http://localhost:8080/tasks/pactStateChange"
:state-change-uses-body false ; defaults to true
:has-pact-with {
:consumer1 {
:pact-file "path/to/provider1-consumer1-pact.json"
}
}
}
}
}
```
If the `:state-change-uses-body` is not specified, or is set to true, then the provider state description will be sent as
JSON in the body of the request. If it is set to false, it will passed as a query parameter.
As for normal requests (see Modifying the requests before they are sent), a state change request can be modified before
it is sent. Set `:state-change-request-filter` to an anonymous function on the provider that will be called before the request is made.
#### Returning values that can be injected (3.6.11+)
You can have values from the provider state callbacks be injected into most places (paths, query parameters, headers,
bodies, etc.). This works by using the V3 spec generators with provider state callbacks that return values. One example
of where this would be useful is API calls that require an ID which would be auto-generated by the database on the
provider side, so there is no way to know what the ID would be beforehand.
There are methods on the consumer DSLs that can provider an expression that contains variables (like '/api/user/${id}'
for the path). The provider state callback can then return a map for values, and the `id` attribute from the map will
be expanded in the expression. For URL callbacks, the values need to be returned as JSON in the response body.
## Filtering the interactions that are verified
You can filter the interactions that are run using three properties: `:pact.filter.consumers`, `:pact.filter.description` and `:pact.filter.providerState`.
Adding `:pact.filter.consumers=:consumer1,:consumer2` to the command line will only run the pact files for those
consumers (consumer1 and consumer2). Adding `:pact.filter.description=a request for payment.*` will only run those interactions
whose descriptions start with 'a request for payment'. `:pact.filter.providerState=.*payment` will match any interaction that
has a provider state that ends with payment, and `:pact.filter.providerState=` will match any interaction that does not have a
provider state.
## Starting and shutting down your provider
For the pact verification to run, the provider needs to be running. Leiningen provides a `do` task that can chain tasks
together. So, by creating a `start-app` and `terminate-app` alias, you could so something like:
$ lein with-profile pact do start-app, pact-verify, terminate-app
However, if the pact verification fails the build will abort without running the `terminate-app` task. To have the
start and terminate tasks always run regardless of the state of the verification, you can assign them to `:start-provider-task`
and `:terminate-provider-task` on the provider.
```clojure
:aliases {"start-app" ^{:doc "Starts the app"}
["tasks to start app ..."] ; insert tasks to start the app here
"terminate-app" ^{:doc "Kills the app"}
["tasks to terminate app ..."] ; insert tasks to stop the app here
}
:pact {
:service-providers {
:provider1 {
:start-provider-task "start-app"
:terminate-provider-task "terminate-app"
:has-pact-with {
:consumer1 {
:pact-file "path/to/provider1-consumer1-pact.json"
}
}
}
}
}
```
Then you can just run:
$ lein with-profile pact pact-verify
and the `start-app` and `terminate-app` tasks will run before and after the provider verification.
## Specifying the provider hostname at runtime [3.0.4+]
If you need to calculate the provider hostname at runtime (for instance it is run as a new docker container or
AWS instance), you can give an anonymous function as the provider host that returns the host name. The function
will receive the provider information as a parameter.
```clojure
:pact {
:service-providers {
:provider1 {
:host #(calculate-host-name %)
:has-pact-with {
:consumer1 {
:pact-file "path/to/provider1-consumer1-pact.json"
}
}
}
}
}
```
Group: au.com.dius Artifact: pact-jvm-provider-lein_2.12
Show all versions Show documentation Show source
Show all versions Show documentation Show source
0 downloads
Artifact pact-jvm-provider-lein_2.12
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 8
Dependencies pact-jvm-provider_2.12, clojure, core.match, leiningen-core, logback-core, logback-classic, httpclient, jansi,
There are maybe transitive dependencies!
Group au.com.dius
Version 3.6.15
Last update 29. April 2020
Organization not specified
URL https://github.com/DiUS/pact-jvm
License Apache 2
Dependencies amount 8
Dependencies pact-jvm-provider_2.12, clojure, core.match, leiningen-core, logback-core, logback-classic, httpclient, jansi,
There are maybe transitive dependencies!
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 31
- 32
- 33
- 34
- 35
- 36
- 37
- 38
- 39
- 40
- 41
- 42
- 43
- 44
- 45
- 46
- 47
- 48
- 49
- 50
- 51
- 52
- 53
- 54
- 55
- 56
- 57
Page 55 from 57 (items total 565)