carbon-identity | This repository is no longer used for development | Configuration Management library

by wso2-attic Java Version: v4.6.0-M2 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | carbon-identity Summary

carbon-identity is a Java library typically used in Devops, Configuration Management applications. carbon-identity has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

| Branch | Build Status | | :------------ |:------------- | master | [Build Status] |. This repository is no longer used for development. Current developments are done in following repositories. This repository contains the source code of modules used for WSO2 Idenity Server 5.1.0 and previous releases. Some of these modules are used by other products of the the platform as well. Service Stubs, Components and Features of each module is contained in this repository.

Support

Quality

Security

License

Reuse

Support

carbon-identity has a low active ecosystem.

It has 20 star(s) with 259 fork(s). There are 62 watchers for this library.

It had no major release in the last 12 months.

There are 1 open issues and 11 have been closed. On average issues are closed in 162 days. There are 39 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of carbon-identity is v4.6.0-M2

Quality

carbon-identity has 0 bugs and 0 code smells.

Security

carbon-identity has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

carbon-identity code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

carbon-identity is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

carbon-identity releases are available to install and integrate.

Build file is available. You can build the component from source.

Top functions reviewed by kandi - BETA

kandi has reviewed carbon-identity and discovered the below as its top functions. This is intended to give you an instant insight into carbon-identity implemented functionality, and help decide if they suit your requirements.

Validates the grant .
Processes the policy DTO and returns an array of strings representing the rules .
Update the local and outbound authentication configuration .
Returns the default policy editor configuration .
Extract metadata from an apply element .
get a group
Build SAML authentication configuration .
This method is used to authenticate a user .
Invokes the dispatch method .
Construct a SCIMObject from a map of attributes .

Get all kandi verified functions for this library.

carbon-identity Key Features

No Key Features are available at this moment for carbon-identity.

carbon-identity Examples and Code Snippets

No Code Snippets are available at this moment for carbon-identity.

Community Discussions

Trending Discussions on carbon-identity

WSO2 - Add local authentication step BEFORE basic auth

WSO2 IS. package org.wso2.identity.sso and SSO SLO fro more than one application

QUESTION

WSO2 - Add local authentication step BEFORE basic auth

Asked 2019-Jun-14 at 12:56

WSO2 5.3.0. I am attempting to put in a local authentication step into my flow BEFORE basic auth runs. This is to aid in upgrading our password hashing algorithm (see this other question I asked)

The problem (I think) I am running into is that the initiateAuthenticationRequest is not being called for my new local authenticator (so username is null at the time, the basic authenticator runs to pop the login screen and fill it in, but my code never reruns).

EDIT: My initiateAuthenticationRequest was being skipped because canHandle was evaluating to true. If the method returns false initiateAuthenticationRequest gets called (Code reference here )

My current conundrum is how to pass the http request parameters onto the next step (the BasicAuthenticator) such that my login screen doesn't show up twice. Any help with this issue is appreciated.

EDIT 2: The request parameters are being passed along, but something else is causing BasicAuthenticator.initiateAuthenticationRequest to be called (see same code reference above). It looks like it is because the attribute "commonAuthHandled" is set to true on the request, but I can't find where that's happening, so help finding THAT is what I'm currently looking for

...

ANSWER

Answered 2019-Jun-14 at 12:56

My solution here was to override the process method (after reading this code more carefully I realized that my step was toggling the commonAuthHandled bit back to true after processing its response)

A little hacky, but it seems to be working

Source https://stackoverflow.com/questions/56395783

QUESTION

WSO2 IS. package org.wso2.identity.sso and SSO SLO fro more than one application

Asked 2017-Sep-02 at 15:59

I can't find source for package org.wso2.carbon.identity.sso.saml. In github repository wso2-attic/carbon-identity there are these classes, but there is note, that repository is no longer used for development and I find there 2 links:

...

ANSWER

Answered 2017-Sep-02 at 15:59

I'm assuming you are looking for SPInitLogoutRequestProcessor. You can find it at [1]. For IS 5.3.0, the SAML component related development happens in the 5.3.x branch.

For your query on SLO; when you have the 2 applications configured for single logout and you logout from one application, the Identity Server is invalidating the user's authenticated session and sends back-channel SAML logout request to the other session participants (App 2 in this case). So the 2nd application should invalidate it's user session upon receiving the logout request from IS.

The error you are seeing should be due to IS not being able to find a valid authenticated session (as the session is already removed) for the logout request. [2] has a detailed explanation on how the single logout happens in IS.

One other approach you can take is to check whether there's an existing authenticated session in the IDP side before sending the logout request. You can use a passive SAML request to check the status of the session and if the session is already there then send the logout request.

Source https://stackoverflow.com/questions/45980383

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install carbon-identity

You can download it from GitHub.
You can use carbon-identity like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the carbon-identity component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: