Sts Eclipse Version

  • Navigation
  • Main Page
  • Community portal
  • Current events
  • Recent changes
  • Random page
  • Help
  1. Sts Eclipse Version
  2. Eclipse Sts Download
  3. Sts Eclipse Version 9
  • Toolbox
  • Page information
  • Permanent link
  • Printable version
  • Special pages
  • Related changes
  • What links here

{{#eclipseproject:technology.higgins eclipse_custom_style.css}}

Click Help Eclipse Marketplace Select the version that matches your Eclipse's version and click Install button. All features are selected by default, click Next. Select I accept the terms of the license agreements, and then click Finish. Feb 12, 2020 Spring Tool Suite (STS) is an Eclipse-based IDE which is optimized for developing Spring framework-based projects. If you are already using Eclipse IDE, you may consider installing STS as a plug-in for your existing Eclipse, because that's faster than downloading the STS separately. Which is better STS or Eclipse?

The Higgins Security Token Service (STS) IdP Solution is an extensible and adaptable framework that implements the OASIS WS-Trust standard and provides support for deployment in a variety of scenarios. It creates relying party consumable Digital Identities from Claim data.

Note: In the Higgins project we sometimes use the term 'Token Service' instead of the commonly used STS (Security Token Service) term.

  • 3Deployer Perspective
  • 4Developer Perspective


This page describes the STS IdP Solution that was released as part of Higgins 1.0 as well as the version of this solution that will be part of Higgins 1.1

End-User Perspective

A running instance of this deployment is available here:

Deployer Perspective


Download and unzip the file for the built web application from one of the builds from here



Developer Perspective


Claim data can either be 'pushed' (passed) in by client code (e.g. I-Card Provider) to the STS and passed in turn to a Token Provider, or the STS can 'pull' (retreive) claim data from the I-Card Provider.

The framework consists of:

  1. a Java implementation of the core engine component along with a set of Java interfaces that describe plug points for components,
  2. a set of Java implementations of platform specific bindings (e.g. Axis 1.x),
  3. a set of Java implementations of security token extensions (e.g. SAML 1.1), and
  4. a web application that faciliates the registration and management of digital subject profiles.

The framework is also dependent on the Higgins Identity Attribute Service (IdAS) and one or more Context Providers (CPs).

The core engine component is configurable through an API; typically invoked by a binding component implementation. The core engine is responsible for loading and configuring security token extensions and Context Providers (Context Providers are registered in the IdAS Registry). When Request Security Token (RST) messages are received, the core engine retrieves a digital subject from a CP via the IdAS, invokes the appropriate security token extension, and returns the RST Response (RSTR). Note that current implementation limitations have caused the reponsibility for retrieval of digital subjects into the token extensions.

Binding components are responsible for loading and configuring the core engine, accepting messages containing RSTs (via SOAP or some other means), performing platform specific processing on inbound messages (e.g. WS-Security, WS-SecurityPolicy, WS-Addressing), converting received messages into a platform independent representation (STSRequest), invoking the core engine to process requests, converting platform independent responses (STSResponse) into platform dependent representation, performing platform specific processing on outbound responses, and returning response messages to the requestor. Note that some applications may directly invoke the core engine, essentially providing their own binding.

Token extensions consist of handler classes that are configurable through an API; typically invoked by the core engine during its own configuration. Token extensions are responsible for processing received STSRequest messages and generating STSResponse messages. In most cases the core engine can decide which extension should handle which message via its configuration. However, in some cases the core may not be able to determin which handler shoud process a message, and handlers may be polled in sequence to determine which should handle a message.

The digital subject profile management web application is intended to provide a CP independent way to manage user profiles. User profiles can be created, modified (e.g. adding/removing identity attributes), and deleted. Additionally, Microsoft CardSpace compatible Information Card may be generated which associates a digital subject on a deployed STS instance with a credential (e.g. username/password, self-signed SAML Assertion).

All of the above components are provided as part of a reference implementation, any of these components can be replaced by an alternative implementation as long as it implements the appropriate interfaces and operational semantics. This reference implementation is evolving to enable new capabilities and deployment scenarios.

Here is an older architecture diagram:


Sts Eclipse Version

Token Service Build Instructions.

Retrieved from ''

The AWS Toolkit for Eclipse is an open source plug-in for the Eclipse Java IDE that makes it easier for developers to develop, debug, and deploy Java applications using Amazon Web Services. With the AWS Toolkit for Eclipse, you’ll be able to get started faster and be more productive when building AWS applications.

1. Open Help → Install New Software….

2. Enter in the text box labeled “Work with” at the top of the dialog.

3. Select the required 'AWS Core Management Tools' and other optional items from the list below.

4. Click “Next.” Eclipse guides you through the remaining installation steps.


Note: The toolkit requires Eclipse 4.4 (Luna) or higher

The AWS Toolkit for Eclipse conveniently includes the AWS SDK for Java, so you can get started building Java applications on AWS infrastructure services in Eclipse, including Amazon S3, Amazon EC2, and Amazon DynamoDB.

Easily create new Java projects using the AWS Java library using one of the project templates, or add the library to an existing project.


Use the Eclipse Java IDE to build and debug your applications.

Automatically download new versions of the SDK through the Eclipse update site.

Easily access and administer your AWS infrastructure, including Amazon S3, Amazon DynamoDB, Amazon EC2, and more while developing your application. The AWS Explorer provides a graphical interface that makes it easy to create, edit, and delete resources.

Create, view, and delete Amazon S3 objects, Amazon DynamoDB items and attributes, Amazon SQS messages, and more.

Add, edit, and delete resources to help build and test your application without leaving the IDE.

Write Select queries against your data in Amazon DynamoDB and edit the results.

Use the AWS Toolkit for Eclipse to develop, debug, then deploy your Java web applications to AWS Elastic Beanstalk.

Create new Java web applications using a web application template, including one based on the Travel Log sample Java web application. Use the Eclipse Java IDE to build and run your application locally before deploying to AWS Elastic Beanstalk.

Easily deploy new application versions to AWS Elastic Beanstalk, then use Amazon EC2 Management in Eclipse or the AWS Management Console to manage the application.

Remotely debug your application running in a Beanstalk environment. The Toolkit helps you select an EC2 instance, automatically configures the security groups and JVM settings, then starts a remote debugging session.

Discover all the features in the User Guide »

Eclipse Sts Download

Connect with other developers in the Java Community Forum »

German tank tree war thunder

Discover more about using Java with AWS in the Java Developer Center »

Sts Eclipse Version 9

Dig through the source code in the GitHub Repository »