[Dev] WSO2 Enterprise Integrator 6.2.0-M3 Released!

Hi All, The WSO2 Integration team is pleased to announce the release of Enterprise Integrator 6.2.0 Milestone 3. Source & binary distribution files of the WSO2 Enterprise Integrator 6.2.0-M3 is available for download from the following location.

Re: [Dev] [GSOC][Siddhi][DEV] Deployment and Code Management of PySiddhi

Hi Madhawa, Merged both PRs and the Wiki. Regards, Grainier. On Wed, Aug 23, 2017 at 9:41 PM, Madhawa Vidanapathirana < madhawavidanapathir...@gmail.com> wrote: > Hi, > > I have sent the new PRs [1] [2] which merge WSO2 DAS Client with PySiddhi. > > The Wiki [3] has also been updated, which

Re: [Dev] Is this fix correct? Can someone explain?

On Thu, Aug 24, 2017 at 1:27 AM Johann Nallathamby wrote: > > https://github.com/wso2/carbon-identity-framework/commit/1f2df5faf2a46258791bdaf1d4c94741626e34a1 > > How is *resourceType* attribute mapped to *userType*? And why is > AttributeID still *mail*? > This is scim2

Re: [Dev] WSO2 Identity Server 5.4.0-M3 Released!

IAM Team, Please note that the following JIRAs have not be fixed per se. According to the comments they have been resolved as "cannot reproduce", "won't fix" or "invalid". But the "Resolution" says "Fixed" which is incorrect. Can we change this and make sure in future we strictly follow proper

[Dev] [IAM] Can't we do the same fix by adding fragment component as a blacklisted pattern to our JS util method?

Can't we do $subject to fix [1]? I thought we were following this as a standard approach in our UI layer so that we can reuse these functionality in all our UIs. This is the approach we were following up until IS 5.3.0. Preventing entering fragment component could be a common requirement when

[Dev] Is this fix correct? Can someone explain?

https://github.com/wso2/carbon-identity-framework/commit/1f2df5faf2a46258791bdaf1d4c94741626e34a1 How is *resourceType* attribute mapped to *userType*? And why is AttributeID still *mail*? Regards, Johann. -- *Johann Dilantha Nallathamby* Senior Lead Solutions Engineer WSO2, Inc.

Re: [Dev] [GSOC][Siddhi][DEV] Deployment and Code Management of PySiddhi

Hi, I have sent the new PRs [1] [2] which merge WSO2 DAS Client with PySiddhi. The Wiki [3] has also been updated, which would require a manual merge since PRs are not possible for GitHub Wikis. Kindly reach me if any changes are required. [1] https://github.com/wso2/PySiddhi/pull/3 [2]

Re: [Dev] Audience(aud) value in OpenID Connect ID Token vs Token Introspection response

On Wed, Aug 23, 2017 at 4:32 AM, Sathya Bandara wrote: > Hi, > > The aud claim in id token is used to identify to which parties the JWT is > intended for. If the client application needs to process the JWT then it > should identify itself as a value in the audiences claim.

Re: [Dev] Audience(aud) value in OpenID Connect ID Token vs Token Introspection response

Hi, The aud claim in id token is used to identify to which parties the JWT is intended for. If the client application needs to process the JWT then it should identify itself as a value in the audiences claim. Therefore it is valid and rational to have the client ID in the audience claim.

Re: [Dev] Request to install mkdocs and mkdocs-material in jenkins.

Thanks Maheshika, If you need any help from us, please let us know, we need to get this done ASAP. Regards Suho On Wed, Aug 23, 2017 at 3:03 PM, Chathurika Amarathunga < chathuri...@wso2.com> wrote: > Thank you Maheshika. > > Regards > Chathurika. > > On Wed, Aug 23, 2017 at 1:58 PM, Maheshika

Re: [Dev] Request to install mkdocs and mkdocs-material in jenkins.

Thank you Maheshika. Regards Chathurika. On Wed, Aug 23, 2017 at 1:58 PM, Maheshika Goonetilleke wrote: > Hi Chathurika > > We need to test this on staging and then install it in production. Will do > so and update this thread. > > On Wed, Aug 23, 2017 at 1:12 PM,

Re: [Dev] Audience(aud) value in OpenID Connect ID Token vs Token Introspection response

The audience of the ID token is the web app (or it can also have the token endpoint - in case of the JWT grant type) - the audience of the access token is the API (or where it will be used by the web app).. so those can be two different values.. This [1] is a good way we should consider

Re: [Dev] Audience(aud) value in OpenID Connect ID Token vs Token Introspection response

Farasath Ahamed Software Engineer, WSO2 Inc.; http://wso2.com Mobile: +94777603866 Blog: blog.farazath.com Twitter: @farazath619 On Wed, Aug 23, 2017 at 1:58 PM, Gayan Gunawardana wrote: > > > On Wed, Aug 23, 2017

Re: [Dev] Request to install mkdocs and mkdocs-material in jenkins.

Hi Chathurika We need to test this on staging and then install it in production. Will do so and update this thread. On Wed, Aug 23, 2017 at 1:12 PM, Chathurika Amarathunga < chathuri...@wso2.com> wrote: > Hi Maheshika, > > We are planing to use MKdocs [1] to generate the documentation site >

Re: [Dev] Audience(aud) value in OpenID Connect ID Token vs Token Introspection response

On Wed, Aug 23, 2017 at 1:58 PM, Gayan Gunawardana wrote: > > > On Wed, Aug 23, 2017 at 1:46 PM, Asela Pathberiya wrote: > >> >> >> On Tue, Aug 22, 2017 at 11:32 AM, Gayan Gunawardana >> wrote: >> >>> According to OpenID connect specification [1]

Re: [Dev] Audience(aud) value in OpenID Connect ID Token vs Token Introspection response

On Wed, Aug 23, 2017 at 1:46 PM, Asela Pathberiya wrote: > > > On Tue, Aug 22, 2017 at 11:32 AM, Gayan Gunawardana > wrote: > >> According to OpenID connect specification [1] "aud" value is client id >> with identifiers for other audiences. >> >> { >>"iss":

Re: [Dev] Audience(aud) value in OpenID Connect ID Token vs Token Introspection response

On Tue, Aug 22, 2017 at 11:32 AM, Gayan Gunawardana wrote: > According to OpenID connect specification [1] "aud" value is client id > with identifiers for other audiences. > > { >"iss": "https://server.example.com;, >"sub": "24400320", >"aud": "s6BhdRkqt3", >

Re: [Dev] Regarding auth_time claim in OIDC id_token

On Wed, Aug 23, 2017 at 12:46 PM, Hasini Witharana wrote: > Hi, > > In the OIDC specification auth_time is defined as below.[1] > > Time when the End-User authentication occurred. Its value is a JSON number > representing the number of seconds from 1970-01-01T0:0:0Z as measured

[Dev] Request to install mkdocs and mkdocs-material in jenkins.

Hi Maheshika, We are planing to use MKdocs [1] to generate the documentation site (github io site) for all repositories (siddhi,, siddhi extension and product-sp) in Data Analytic team. It is required to install followings to ensure that site is generate at building time [2]. *- python* * -

[Dev] Regarding auth_time claim in OIDC id_token

Hi, In the OIDC specification auth_time is defined as below.[1] Time when the End-User authentication occurred. Its value is a JSON number representing the number of seconds from 1970-01-01T0:0:0Z as measured in UTC until the date/time. When a max_age request is made or when auth_time is

Re: [Dev] [Architecture] WSO2 Stream Processor 4.0.0-M10 Released !

On Wed, Aug 23, 2017 at 4:05 AM, Niveathika Rajendran wrote: > Hi All, > > > The WSO2 Analytics team is pleased to announce the release of *WSO2 > Stream Processor Version 4.0.0 Milestone 10*. > > WSO2 Smart Analytics let digital business creating real-time, intelligent, >