[Dev] [IDENTITY-6155] Invoking the user info endpoint without properly setting the 'Bearer' header causes server errors

Hi, I am working on the jira IDENTITY-6155 . When Invoking the user info endpoint without adding the access token to the 'Bearer' header causes the server to return an ArrayIndexOutOfBoundsException with the full stacktrace to the client. As per the

Re: [Dev] Please review and merge the pull request

On Fri, Jul 28, 2017 at 6:29 PM, Dewni Weeraman wrote: > > Hi, > > Please merge the pull request [1] which contains the fix for [2]. > > [1] - https://github.com/wso2/carbon-kernel/pull/1456 > > This PR is already merged. Is this

Re: [Dev] jndi.properties Production Recommended Configuration

Thank you! 2017-07-28 6:40 GMT-03:00 Sashika Wijesinghe : > Hi Junior, > > The connection details you have used are correct for failover scenarios. > Refer [1] to get more information about MB failover handling. > > > [1] https://docs.wso2.com/display/MB320/Handling+Failover >

Re: [Dev] Please review and merge the pull request

Hi Farasath, It seems like the PR **url** is correct but the hyperlink is wrong. Just adding the PR link again to avoid the confusion. https://github.com/wso2/carbon-kernel/pull/1456 Regards, On Fri, Jul 28, 2017 at 6:58 PM, Farasath Ahamed wrote: > > > > On Fri, Jul 28,

[Dev] Please review and merge the pull request

Hi, Please merge the pull request [1] which contains the fix for [2]. [1] - https://github.com/wso2/carbon-kernel/pull/1456 [2] - https://github.com/wso2/carbon-kernel/issues/1455 Regards, Dewni Weeraman -- *Dewni Weeraman* Trainee Software

Re: [Dev] [GSoC 2017][IS] SCIM 2.0 Compliance Test Suite

Hi, As I demonstrated at the demo held today, I have been able to complete a milestone of the project as per the timeline. As decided at the meeting, I sent a PR[1] to the scim2-compliance-test-suite repo. Please review and merge. As I explained at the meeting, the current implementation[1]

Re: [Dev] Identity Server - Problems implementing a custom JDBC user store

Hello Nuwandi, Thank you for your answer. Actually, I found the current implementation from the org.wso2.carbon.identity.user.store.count_5.7.5.jar located in /repository/components/plugins from where I found which dependency to add to my POM and tried to implement one myself but that did not

[Dev] [IS] Introducing a new attribute in CacheConfig for persistence

Hi, What do you think about introducing $subject to selectively persist each and every cache we have? Right now I think all the caches are controlled by just two attributes "SessionDataPersist.Enabled" and "SessionDataPersist.Temporary". This classification is too broad I think with the recent

Re: [Dev] Configuring Subject Claim URI for File based Service Provider didn't work and no proper documentation to get it done

HI Johann, Created a Jira to track the issue [1]. Will fix this with IS 5.4.0 Thanks Isura. [1] https://wso2.org/jira/browse/IDENTITY-6192 On Wed, Jul 19, 2017 at 2:29 PM, Samuel Gnaniah wrote: > Ack for docs. Can we get some content for this? > > *Samuel Gnaniah* > Lead

Re: [Dev] [IDENTITY-3355] Better if only warning is shown for signature verification failures

+1 for using warning message without the stack trace. But we have to add as much as context info to the log so that the life will be easier when coming to support front. On Fri, Jul 28, 2017 at 1:30 PM, Isura Karunaratne wrote: > Hi Sugirjan, > > +1 for the warning message

Re: [Dev] IS User Portal is validating audience against Carbon SAML2 SSO authenticator defined in authenticator.xml

Let's consider this as the time permits. @Johann can you please create a Jira? On Fri, Jul 28, 2017 at 1:38 PM, Isura Karunaratne wrote: > Adding Rushmin > > On Tue, Jul 18, 2017 at 10:22 AM, Johann Nallathamby > wrote: > >> Hi All, >> >> We noticed $subject.

[Dev] The input stream for an incoming message is null - EI 6.1.1

Hi, I have problem with call mediator. In my scenario I call backend using call mediator with option blocking=true. From backend I got response and next I call another proxy using call mediator with option blocking=true. Then I get error: org.apache.axis2.AxisFault: The input stream for an

Re: [Dev] [IDENTITY-3355] Better if only warning is shown for signature verification failures

Hi Sugirjan, +1 for the warning message without printing the exception trace. We can add exception trace as a debug log. Thanks Isura. On Thu, Jul 20, 2017 at 6:47 PM, Sugirjan Ragunaathan wrote: > Hi, > > I'm working on the WSO2 public JIRA issue $subject [1]. > > In the

Re: [Dev] IS User Portal is validating audience against Carbon SAML2 SSO authenticator defined in authenticator.xml

Adding Rushmin On Tue, Jul 18, 2017 at 10:22 AM, Johann Nallathamby wrote: > Hi All, > > We noticed $subject. I don't think this is valid because IS User Portal > and Carbon management console should be treated as two SPs. So user portal > reading the audience from

Re: [Dev] (IDENTITY-6167) Need to honor modifications to email-admin-config.xml file

Can we move configuration files in a minor release? Thanks Isura. On Thu, Jul 27, 2017 at 12:26 PM, KasunG Gajasinghe wrote: > > > On Thu, Jul 27, 2017 at 10:20 AM, Harsha Thirimanna > wrote: > >> >> >> On Thu, Jul 27, 2017 at 9:41 AM, KasunG Gajasinghe

Re: [Dev] The input stream for an incoming message is null - EI 6.1.1

Hi, Could you please share your ESB config? On Fri, Jul 28, 2017 at 1:50 PM, Melodias wrote: > Hi, > > I have problem with call mediator. In my scenario I call backend using call > mediator with option blocking=true. From backend I got response and next I > call

Re: [Dev] [IDENTITY-3355] Better if only warning is shown for signature verification failures

Hi all, We log full trace in debug/error levels, but no trace in warn/info levels. e.g. catch (IdentitySAML2SSOException e) { if (log.isDebugEnabled()) { log.debug("Signature validation failed for the SAML Message : Failed to construct the X509CredentialImpl for the alias : " +

Re: [Dev] [IS] Introducing a new attribute in CacheConfig for persistence

On Fri, Jul 28, 2017 at 12:42 PM, Johann Nallathamby wrote: > Hi, > > What do you think about introducing $subject to selectively persist each > and every cache we have? Right now I think all the caches are controlled by > just two attributes "SessionDataPersist.Enabled" and >

Re: [Dev] The input stream for an incoming message is null - EI 6.1.1

Thanks for reply That's my inSequence: http://esp.ws/;> CODE_$1 pl

Re: [Dev] [IS] Introducing a new attribute in CacheConfig for persistence

Do you think we can live with these two kind of caches only? I am not sure. May be others from IAM team can chip in. My objective is to use sticky sessions as much as possible and persist as less as possible, make the flows optimized. If there are no limitations in this I am fine. E.g. SAML2 SSO

Re: [Dev] [IS] Introducing a new attribute in CacheConfig for persistence

On Fri, Jul 28, 2017 at 2:56 PM, Johann Nallathamby wrote: > Do you think we can live with these two kind of caches only? I am not sure. > Above properties for only the caches which are in framework. Basically to handle the end user's session related stuff.. I do not think we

Re: [Dev] jndi.properties Production Recommended Configuration

Hi Junior, The connection details you have used are correct for failover scenarios. Refer [1] to get more information about MB failover handling. [1] https://docs.wso2.com/display/MB320/Handling+Failover On Thu, Jul 27, 2017 at 7:04 PM, Júnior wrote: > Hi everyone, > >

Re: [Dev] [IS] Introducing a new attribute in CacheConfig for persistence

On Fri, Jul 28, 2017 at 3:07 PM, Asela Pathberiya wrote: > > > On Fri, Jul 28, 2017 at 2:56 PM, Johann Nallathamby > wrote: > >> Do you think we can live with these two kind of caches only? I am not >> sure. >> > > Above properties for only the caches which are

Re: [Dev] IS User Portal is validating audience against Carbon SAML2 SSO authenticator defined in authenticator.xml

Created - https://wso2.org/jira/browse/IDENTITY-6193 On Fri, Jul 28, 2017 at 1:44 PM, Rushmin Fernando wrote: > Let's consider this as the time permits. > > @Johann can you please create a Jira? > > On Fri, Jul 28, 2017 at 1:38 PM, Isura Karunaratne wrote: >

Re: [Dev] IS User Portal is validating audience against Carbon SAML2 SSO authenticator defined in authenticator.xml

Thanks ! On Fri, Jul 28, 2017 at 3:31 PM, Johann Nallathamby wrote: > Created - https://wso2.org/jira/browse/IDENTITY-6193 > > On Fri, Jul 28, 2017 at 1:44 PM, Rushmin Fernando > wrote: > >> Let's consider this as the time permits. >> >> @Johann can you

[Dev] [GSOC 2017][API Manager ][Environment Support][Meeting Min]

Hi all Meeting Min - Discussed on the UI part with and got feedback from UI-expert on what to change. - Also discussed about getting a configuration map. - Did the append part for the tokens and the Ms4j token also discussed on the editing the path. Thank you Ravindu Perera.

Re: [Dev] [GSoC 2017][IS] SCIM 2.0 Compliance Test Suite

Hi VIndula, Impressive progress so far..!! As discussed let's have more focus on the the maximizing re-usability aspects of this test suite. So the test suit will be easy to tryout, easy to contribute & easy to integrate with test automation frameworks.. Regards, On Fri, Jul 28, 2017 at 8:55