Hi Gayan,
Currently working on the configuration option. Sure I'll move changes to
*identity-outbound-provisioning-scim*.
Best Regards
Isuranga Perera
On Mon, Feb 12, 2018 at 11:59 AM, Gayan Gunawardana wrote:
> Hi Isuranga,
>
> Could you be able to move
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180213T053000Z
DTEND:20180213T063000Z
DTSTAMP:20180212T051557Z
ORGANIZER;CN=indu...@wso2.com:mailto:indu...@wso2.com
UID:7qnie84b1epvq6ogvi45hrp...@google.com
Hi Eranda,
Design-wise I'm more in favor of Design 2 where commands feel more natural
(` list exchange` as opposed to ` exchange list`). This would be
a bit more complex to implement in terms of code, but IMO UX is better with
design 2. This aligns to both WUM approach (which is a pattern most
hi Azeez
Please confirm.
On Mon, Feb 12, 2018 at 10:26 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:
> Hi Maheshika,
>
> Can you please create a new git repository with the name "
> identity-x509-revocation" under wso2-extensions, for moving this feature
> implementation.
>
> Thanks
Hi Maheshika,
Can you please create a new git repository with the name "
identity-x509-revocation" under wso2-extensions, for moving this feature
implementation.
Thanks and Regards
On Wed, Jan 17, 2018 at 11:20 AM, Indunil Upeksha Rathnayake <
indu...@wso2.com> wrote:
> Hi,
>
> Please find the
Hi Dakshika,
Claim management via a REST API is not supported yet. Currently, it is
supported with SOAP.
Thank you for pointing out 409 and updated the .yml at appropriate places.
Thank You.
On Mon, Feb 12, 2018 at 8:49 AM, Dakshika Jayathilaka
wrote:
> Hi Chiran,
>
>
Hi Chiran,
Aren't we support for adding local claim via REST API?
Also, don't we need to add "409 conflicts" for the scenarios that resource
already exists?
Regards,
*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Associate Technical Lead
WSO2, Inc.
lean.enterprise.middleware