spase-locker

The SP base for CIP(Cloud Integration Platform)

License	The Apache Software License, Version 2.0
Categories	Net
GroupId	com.soterianetworks
ArtifactId	spase-locker
Last Version	0.9.59
Release Date	Dec 30, 2020
Type	jar
Description	spase-locker The SP base for CIP(Cloud Integration Platform)
Project URL	http://soterianetworks.com

Download spase-locker

Filename	Size
spase-locker-0.9.59.pom
spase-locker-0.9.59.jar	9 KB
spase-locker-0.9.59-sources.jar	7 KB
spase-locker-0.9.59-javadoc.jar	80 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/com.soterianetworks/spase-locker/ -->
<dependency>
    <groupId>com.soterianetworks</groupId>
    <artifactId>spase-locker</artifactId>
    <version>0.9.59</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/com.soterianetworks/spase-locker/
implementation 'com.soterianetworks:spase-locker:0.9.59'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.soterianetworks/spase-locker/
implementation ("com.soterianetworks:spase-locker:0.9.59")

Apache Buildr

'com.soterianetworks:spase-locker:jar:0.9.59'

Apache Ivy

<dependency org="com.soterianetworks" name="spase-locker" rev="0.9.59">
  <artifact name="spase-locker" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='com.soterianetworks', module='spase-locker', version='0.9.59')
)

Scala SBT

libraryDependencies += "com.soterianetworks" % "spase-locker" % "0.9.59"

Leiningen

[com.soterianetworks/spase-locker "0.9.59"]

Dependencies

compile (3)

Group / Artifact	Type	Version
commons-logging : commons-logging	jar	1.1.3
org.apache.commons : commons-lang3	jar	3.8.1
com.google.guava : guava	jar	23.0

provided (1)

Group / Artifact	Type	Version
org.springframework.boot : spring-boot-starter	jar	1.5.21.RELEASE

Project Modules

There are no modules declared in this project.

Overview

The SP (Service Provider) base library for integration with Soteria Networks CIP (Cloud Integration Platform) .

https://mvnrepository.com/artifact/com.soterianetworks

Integration Modes

There are three ways to integrate a SP to the CIP.

Integration Mode	Description
CIP Managed	Everything is managed by CIP (db, cache, messaging ...)
	Deployed as part of the CIP, usually a platform service.
SP Managed	Everything is managed by SP (db, cache, messaging ...)
	The user authn & authz are delegated to CIP
	The frontend is integrated with CIP by way of OAuth2 IMPLICIT grant_type.
	* The micro service provided by SP will register to CIP's registry
	* The frontend accesses the micro service through CIP gateway
Standalone	Everything is managed by SP (db, cache, messaging ...)
	The user authn & authz are delegated to CIP
	The frontend is integrated with CIP by way of OAuth2 IMPLICIT grant_type.
	* SP manages the backend micro service by itself
	* The frontend accesses the backend micro service directly

Soteria Networks Inc.

Versions

Version
0.9.59 Dec 30, 2020
0.9.58 Dec 29, 2020
0.9.57 Dec 29, 2020
0.9.56 Dec 28, 2020
0.9.55 Dec 28, 2020
0.9.54 Dec 28, 2020