date:20171104

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

2017-11-04 Thread Johann Nallathamby

Again I think we've missed the point to explain why we need to define
claims to get this feature working. If that was explained, naturally a user
will think when he is sending a request using SCIM APIs whether he has
included these claims also. And then he will follow that by thinking if he
has done the claim mappings properly; if he understands how IS and claim
mappings work. Making him understand that is not part of this section; what
we can do here is, may be link to the section on claim management. This
will keep this section concise and clear. Because it won't scale if we go
to give instructions for every protocol/dialect we have. And I think in
another conversation we said we will remove anything related to APIs from
the deep dive pages and have it only in the developer section.

If you still think we may need more hand holding of the user then we can
have a tutorial section for this - "Identity Administration with SCIM".

Regards,
Johann.

On Fri, Nov 3, 2017 at 9:37 PM, Sathya Bandara  wrote:

> Hi Sashika,
>
> I guess the documentation is missing some configuration details. The
> askPassword and verifyEmail extension attributes should be configured in
> $SERVER_HOME/repository/conf/scim-schema-extension.config file in
> addition to the other extension attributes which are already defined there,
> as follows.
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:
> wso2Extension.askPassword",
> "attributeName":"askPassword",
> "dataType":"boolean",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"The User's manager",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"null"
> },
>
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:
> wso2Extension.verifyEmail",
> "attributeName":"verifyEmail",
> "dataType":"boolean",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"The User's manager",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"null"
> },
>
> These two attributes should be added to the list of subAttributes of the
> urn:scim:schemas:extension:wso2:1.0 entry which can be find at the end of
> the scim-schema-extension.config file as shown below.
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0",
> "attributeName":"wso2Extension",
> "dataType":"null",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"SCIM wso2 User Schema Extension",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"employeeNumber costCenter organization division
> department manager askPassword verifyEmail"
> }
>
>
> Also The correct approach to create claim mappings for SCIM extension
> attributes is by configuring external claims for the default SCIM dialect
> (scim:schemas:core:1.0) and not by creating a separate dialect for the
> extension schema (scim:schemas:extension:wso2:1.0:wso2Extension). This is
> already identified in [1] and the relevant documents has been updated.
> Please refer Claim Mapping section in [2]. Also I will create a Doc JIRA to
> improve the documentation with necessary configuration details in [3].
>
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-4647
> [2] https://docs.wso2.com/display/IS530/Extensible+SCIM+User+
> Schemas+With+WSO2+Identity+Server
> [3] https://docs.wso2.com/display/IS530/Creating+Users+using+
> the+Ask+Password+Option
>
> Thanks,
> Sathya
>
>
>
> On Fri, Nov 3, 2017 at 2:46 PM, Sashika Wijesinghe 
> wrote:
>
>> Hi All,
>>
>> I want to create users with ask password option using SCIM 1.1. I have
>> configured the server as documented in [1].
>>
>> The below curl command is used to create the user. After executing the
>> curl command, the user created successfully but did not receive any email
>> notification for the given email address. This works when I created a user
>> from the management console and SOAP admin service.
>>
>> Do we need any further configurations to get this done with SCIM 1.1?
>>
>> curl -v -k --user admin:admin --data "{"schemas":[],"userName":"nee
>> ls","password":"password","wso2Extension":{"askPassword":"
>> true"},"emails":"sash...@wso2.com"}" --header
>> "Content-Type:application/json" https://localhost:9444/wso2/scim/Users
>>
>> [1] https://docs.wso2.com/display/IS530/Creating+Users+using
>> +the+Ask+Password+Option
>>
>> Thanks
>> Sashika
>>
>>
>>
>>
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>
>
>
> --
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
> <+94%2071%20411%205032>
>



-- 
Thanks & Regards,

*Johann Dilantha Nallathamby*
Senior Lead Solutions Engineer
WSO2, Inc.

Re: [Dev] RabbitMQ connection related errors on WSO2 startup

2017-11-04 Thread Vinod Kavinda

Hi Noberto,
I'm not sure how the *rabbitMQ *clusters are working. But based on the
error the EI has connected to your *rabbit@node2.site1 *as the error
suggested, and this error since it is down. I think this is something to do
with your rabbitMQ cluster because if you have configured to node1, there
is no way that EI can get node2 details if that was not some redirection by
the cluster :)

Regards,
Vinod

On Fri, Nov 3, 2017 at 7:20 PM, Norberto Fernandes 
wrote:

> Hi,
>
> Any ideias on the below issue?
> Already tried to run the IE with SNAPSHOT versions of axis and rabbitmq
> jar files but had the same outcome.
>
> This looks like a main issue for scenarios where we have one wso2 node
> connecting to rabbitmq cluster.
>
> Regards,
> Norberto
>
> On 2 Nov 2017, at 16:09, Norberto Fernandes 
> wrote:
>
> Hi all,
>
> I am getting some strange errors while starting up the WSO2 6.1.1 server.
> Hope that you can help.
>
> So, I have a single node WSO2 Server running and connecting to a RabbitMQ
> node (rmqNode1) that is part of a cluster of two (rmqNode1 and rmqNode2).
> Have in mind that all the transportSender and listeners are pointing to
> rmqNode1. No connection details are defined for rmqNode2.
>
>
> If I have the two RabbitMQ cluster nodes up and running and start the WSO2
> 6.1.1 server there isn’t any issue.
> With all servers up, if I shutdown rmqNode2, all continues ok with no
> errors.
>
> If I only have rmqNode1 up and then start WSO2 6.1.1, I get a endless
> stream of errors like :
> TID: [-1] [] [2017-11-02 15:34:48,232] ERROR 
> {org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
> -  Error, Connection already closed myProxysample, Listner id - 78
> {org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
> com.rabbitmq.client.AlreadyClosedException: channel is already closed due
> to channel error; protocol method: #method(reply-code=404,
> reply-text=NOT_FOUND - home node '*rabbit@node2.site1*' of durable queue
> ’sample.queue' in vhost ’sample' is down or inaccessible, class-id=50,
> method-id=10)
> at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:198)
> at com.rabbitmq.client.impl.AMQChannel.rpc(AMQChannel.java:244)
> at com.rabbitmq.client.impl.AMQChannel.privateRpc(AMQChannel.java:222)
> at com.rabbitmq.client.impl.AMQChannel.exnWrappingRpc(AMQChannel.java:117)
> at com.rabbitmq.client.impl.ChannelN.queueDeclare(ChannelN.java:925)
> at com.rabbitmq.client.impl.recovery.AutorecoveringChannel.queueDeclare(
> AutorecoveringChannel.java:332)
> at org.apache.axis2.transport.rabbitmq.utils.RabbitMQUtils.
> declareQueue(RabbitMQUtils.java:213)
> at org.apache.axis2.transport.rabbitmq.ServiceTaskManager$
> MessageListenerTask.initConsumer(ServiceTaskManager.java:527)
> at org.apache.axis2.transport.rabbitmq.ServiceTaskManager$
> MessageListenerTask.run(ServiceTaskManager.java:335)
> at org.apache.axis2.transport.base.threads.NativeWorkerPool$
> 1.run(NativeWorkerPool.java:172)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(
> ThreadPoolExecutor.java:1149)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(
> ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748)
> TID: [-1234] [] [2017-11-02 15:34:48,267]  INFO {
> org.apache.tomcat.util.net.NioSelectorPool} -  Using a shared selector
> for servlet write/read {org.apache.tomcat.util.net.NioSelectorPool}
> TID: [-1] [] [2017-11-02 15:34:48,303]  INFO 
> {org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
> -  Successfully reconnected to RabbitMQ Broker for the
> service myProxysampleSecond, Listner id - 78 {org.apache.axis2.transport.
> rabbitmq.ServiceTaskManager}
> TID: [-1] [] [2017-11-02 15:34:48,243] ERROR 
> {org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
> -  Error, Connection already closed STD.cacheXRefReceiver.1.0.0, Listner id
> - 77 {org.apache.axis2.transport.rabbitmq.ServiceTaskManager}
> com.rabbitmq.client.AlreadyClosedException: channel is already closed due
> to channel error; protocol method: #method(reply-code=404,
> reply-text=NOT_FOUND - home node *'rabbit@node2.site1*' of durable queue
> ’second.sample.queue' in vhost 'sample' is down or inaccessible,
> class-id=50, method-id=10)
> at com.rabbitmq.client.impl.AMQChannel.ensureIsOpen(AMQChannel.java:198)
>
> Please note that node2.site1 is the hostname for rmqNode2.
> I don’t think the server should complain about this. The node that is used
> on the transport configuration is always node1.
>
>
> Any ideias on what may be incorrect? Or can be done ?
> I didn’t find any connection parameter that is related to cluster setup,
> is there any?
>
>
> Many thanks in advance.
>
> Norberto
>
>
>
> ___
> Dev mailing list
> Dev@wso2.org
> http://wso2.org/cgi-bin/mailman/listinfo/dev
>
>


-- 
Vinod Kavinda
Senior Software Engineer
*WSO2 Inc. - lean . enterprise . middleware .*
Mobile : +94 (0) 712 415544

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

2017-11-04 Thread Sathya Bandara

On Nov 4, 2017 12:27 PM, "Sashika Wijesinghe"  wrote:

Hi Sathya,

Thanks for the configuration requirements provided above. It helps to
resolve the issue.

According to the current implementation, since we are mapping the claims
for SCIM extension isn't it better to have the claim configurations mapped
in the scim-schema-extension.config itself when we bundle the pack rather
than asking the user to add these configurations manually?


+1 to this. I think we should provide the relevant claim mappings OOTB for
the extension attributes which are already defined in
scim-sceham-extension.config other than default scim attributes, including
these two attributes. If the user wants to define custom extension
attributes then we can provide necessary configuration details to do claim
mappings with local claims.

Thanks,
Sathya


Thanks
Sashika



On Fri, Nov 3, 2017 at 9:37 PM, Sathya Bandara  wrote:

> Hi Sashika,
>
> I guess the documentation is missing some configuration details. The
> askPassword and verifyEmail extension attributes should be configured in
> $SERVER_HOME/repository/conf/scim-schema-extension.config file in
> addition to the other extension attributes which are already defined there,
> as follows.
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:wso2Exte
> nsion.askPassword",
> "attributeName":"askPassword",
> "dataType":"boolean",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"The User's manager",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"null"
> },
>
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:wso2Exte
> nsion.verifyEmail",
> "attributeName":"verifyEmail",
> "dataType":"boolean",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"The User's manager",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"null"
> },
>
> These two attributes should be added to the list of subAttributes of the
> urn:scim:schemas:extension:wso2:1.0 entry which can be find at the end of
> the scim-schema-extension.config file as shown below.
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0",
> "attributeName":"wso2Extension",
> "dataType":"null",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"SCIM wso2 User Schema Extension",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"employeeNumber costCenter organization division
> department manager askPassword verifyEmail"
> }
>
>
> Also The correct approach to create claim mappings for SCIM extension
> attributes is by configuring external claims for the default SCIM dialect
> (scim:schemas:core:1.0) and not by creating a separate dialect for the
> extension schema (scim:schemas:extension:wso2:1.0:wso2Extension). This is
> already identified in [1] and the relevant documents has been updated.
> Please refer Claim Mapping section in [2]. Also I will create a Doc JIRA to
> improve the documentation with necessary configuration details in [3].
>
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-4647
> [2] https://docs.wso2.com/display/IS530/Extensible+SCIM+User+Sch
> emas+With+WSO2+Identity+Server
> [3] https://docs.wso2.com/display/IS530/Creating+Users+using+the
> +Ask+Password+Option
>
> Thanks,
> Sathya
>
>
>
> On Fri, Nov 3, 2017 at 2:46 PM, Sashika Wijesinghe 
> wrote:
>
>> Hi All,
>>
>> I want to create users with ask password option using SCIM 1.1. I have
>> configured the server as documented in [1].
>>
>> The below curl command is used to create the user. After executing the
>> curl command, the user created successfully but did not receive any email
>> notification for the given email address. This works when I created a user
>> from the management console and SOAP admin service.
>>
>> Do we need any further configurations to get this done with SCIM 1.1?
>>
>> curl -v -k --user admin:admin --data "{"schemas":[],"userName":"nee
>> ls","password":"password","wso2Extension":{"askPassword":"tr
>> ue"},"emails":"sash...@wso2.com"}" --header
>> "Content-Type:application/json" https://localhost:9444/wso2/scim/Users
>>
>> [1] https://docs.wso2.com/display/IS530/Creating+Users+using
>> +the+Ask+Password+Option
>>
>> Thanks
>> Sashika
>>
>>
>>
>>
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>
>
>
> --
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
> <+94%2071%20411%205032>
>



-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

2017-11-04 Thread Johann Nallathamby

On Sat, Nov 4, 2017 at 12:27 PM, Sashika Wijesinghe 
wrote:

> Hi Sathya,
>
> Thanks for the configuration requirements provided above. It helps to
> resolve the issue.
>
> According to the current implementation, since we are mapping the claims
> for SCIM extension isn't it better to have the claim configurations mapped
> in the scim-schema-extension.config itself when we bundle the pack rather
> than asking the user to add these configurations manually?
>

+1. I think we have discussed this several other mail threads as well;
can't seem to find them now. Basically we need to have default mappings for
all the identity claims we use in IS such as ask password, email
verification, etc., including for OOTB connectors, and have OOTB mappings
to these identity claims in OIDC, SCIM and other standard dialects we use
in the inbound side (we can omit the Identity Provider dialects like
Facebook, LinkedIn, etc. which is only used in outbound side).

[1] "[IAM] Pre-configure "Identity Claim" mappings for widely used Local
Authenticators"

Regards,
Johann.


>
> Thanks
> Sashika
>
>
>
> On Fri, Nov 3, 2017 at 9:37 PM, Sathya Bandara  wrote:
>
>> Hi Sashika,
>>
>> I guess the documentation is missing some configuration details. The
>> askPassword and verifyEmail extension attributes should be configured in
>> $SERVER_HOME/repository/conf/scim-schema-extension.config file in
>> addition to the other extension attributes which are already defined there,
>> as follows.
>>
>> {
>> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:wso2Exte
>> nsion.askPassword",
>> "attributeName":"askPassword",
>> "dataType":"boolean",
>> "multiValued":"false",
>> "multiValuedAttributeChildName":"null",
>> "description":"The User's manager",
>> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
>> "readOnly":"false",
>> "required":"false",
>> "caseExact":"false",
>> "subAttributes":"null"
>> },
>>
>>
>> {
>> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:wso2Exte
>> nsion.verifyEmail",
>> "attributeName":"verifyEmail",
>> "dataType":"boolean",
>> "multiValued":"false",
>> "multiValuedAttributeChildName":"null",
>> "description":"The User's manager",
>> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
>> "readOnly":"false",
>> "required":"false",
>> "caseExact":"false",
>> "subAttributes":"null"
>> },
>>
>> These two attributes should be added to the list of subAttributes of the
>> urn:scim:schemas:extension:wso2:1.0 entry which can be find at the end
>> of the scim-schema-extension.config file as shown below.
>>
>> {
>> "attributeURI":"urn:scim:schemas:extension:wso2:1.0",
>> "attributeName":"wso2Extension",
>> "dataType":"null",
>> "multiValued":"false",
>> "multiValuedAttributeChildName":"null",
>> "description":"SCIM wso2 User Schema Extension",
>> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
>> "readOnly":"false",
>> "required":"false",
>> "caseExact":"false",
>> "subAttributes":"employeeNumber costCenter organization division
>> department manager askPassword verifyEmail"
>> }
>>
>>
>> Also The correct approach to create claim mappings for SCIM extension
>> attributes is by configuring external claims for the default SCIM dialect
>> (scim:schemas:core:1.0) and not by creating a separate dialect for the
>> extension schema (scim:schemas:extension:wso2:1.0:wso2Extension). This
>> is already identified in [1] and the relevant documents has been updated.
>> Please refer Claim Mapping section in [2]. Also I will create a Doc JIRA to
>> improve the documentation with necessary configuration details in [3].
>>
>>
>> [1] https://wso2.org/jira/browse/DOCUMENTATION-4647
>> [2] https://docs.wso2.com/display/IS530/Extensible+SCIM+User+Sch
>> emas+With+WSO2+Identity+Server
>> [3] https://docs.wso2.com/display/IS530/Creating+Users+using+the
>> +Ask+Password+Option
>>
>> Thanks,
>> Sathya
>>
>>
>>
>> On Fri, Nov 3, 2017 at 2:46 PM, Sashika Wijesinghe 
>> wrote:
>>
>>> Hi All,
>>>
>>> I want to create users with ask password option using SCIM 1.1. I have
>>> configured the server as documented in [1].
>>>
>>> The below curl command is used to create the user. After executing the
>>> curl command, the user created successfully but did not receive any email
>>> notification for the given email address. This works when I created a user
>>> from the management console and SOAP admin service.
>>>
>>> Do we need any further configurations to get this done with SCIM 1.1?
>>>
>>> curl -v -k --user admin:admin --data "{"schemas":[],"userName":"nee
>>> ls","password":"password","wso2Extension":{"askPassword":"tr
>>> ue"},"emails":"sash...@wso2.com"}" --header
>>> "Content-Type:application/json" https://localhost:9444/wso2/scim/Users
>>>
>>> [1] https://docs.wso2.com/display/IS530/Creating+Users+using
>>> +the+Ask+Password+Option
>>>
>>> Thanks
>>> Sashika
>>>
>>>
>>>
>>>
>>> --
>>>
>>> *Sashika WijesingheSoftware Engineer - QA Team*
>>> Mobile : +94 (0) 774537487
>>> sash...@wso2.com
>>>
>>

Re: [Dev] [APIM] [C5] package-lock.json files are untracked

2017-11-04 Thread Chanaka Jayasena

Package-lock is to generate the exact node modules tree when there are
chain dependency version mismatches. Configuring the .npmrc to ignore the
lock file is fixing the build breaks (We have config this in the publisher
app ). But recommended approach is to commit the package-lock.json file so
that the one committing the lock file can exactly project the node-modules
tree on the one who's taking the checkout.

thanks,
Chanaka

On Fri, Nov 3, 2017 at 7:35 PM, Harsha Kumara  wrote:

> Adding Chanka.
>
> @Chanka what would be the best here. To ignore or commit it? @Menuka it
> seems we can ignore it from the .gitignire as per you reference issues.
> Let's add a pull request and fix it.
>
> On Thu, Nov 2, 2017 at 1:41 PM, Menuka Warushavithana 
> wrote:
>
>> Hi all,
>> I have created a GitHub issue for $subject. [1]
>> AFAIK package-lock.json files should either be committed or ignored
>> (added to .gitignore) to avoid unexpected results. [2]
>> Or the generation of package-lock.json could be disabled altogether by
>> adding the line 'package-lock=false' to the .npmrc file. [3]
>>
>>
>> [1] https://github.com/wso2/carbon-apimgt/issues/4676
>> [2] https://github.com/nodejs/citgm/issues/451
>> [3] https://github.com/hapijs/contrib/issues/114
>>
>> Regards
>>
>> *Menuka Warushavithana*
>> *Software Engineering Intern*
>> *WSO2*
>>
>> *Moblie:  + <%2B%2094%2011%202145345%20%C2%A0Ext.%205737> 94 77
>> 6979690*
>> *LinkedIn:   **https://www.linkedin.com/in/menukawarushavithana/
>> *
>> *GitHub:  **https://github.com/menuka94/
>> *
>>
>>
>>
>
>
> --
> Harsha Kumara
> Software Engineer, WSO2 Inc.
> Mobile: +94775505618 <+94%2077%20550%205618>
> Blog:harshcreationz.blogspot.com
>



-- 
Chanaka Jayasena
Associate Tech Lead,
email: chan...@wso2.com; cell: +94 77 4464006
blog: http://chanaka3d.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

2017-11-04 Thread Sashika Wijesinghe

Hi Sathya,

Thanks for the configuration requirements provided above. It helps to
resolve the issue.

According to the current implementation, since we are mapping the claims
for SCIM extension isn't it better to have the claim configurations mapped
in the scim-schema-extension.config itself when we bundle the pack rather
than asking the user to add these configurations manually?

Thanks
Sashika



On Fri, Nov 3, 2017 at 9:37 PM, Sathya Bandara  wrote:

> Hi Sashika,
>
> I guess the documentation is missing some configuration details. The
> askPassword and verifyEmail extension attributes should be configured in
> $SERVER_HOME/repository/conf/scim-schema-extension.config file in
> addition to the other extension attributes which are already defined there,
> as follows.
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:
> wso2Extension.askPassword",
> "attributeName":"askPassword",
> "dataType":"boolean",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"The User's manager",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"null"
> },
>
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0:
> wso2Extension.verifyEmail",
> "attributeName":"verifyEmail",
> "dataType":"boolean",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"The User's manager",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"null"
> },
>
> These two attributes should be added to the list of subAttributes of the
> urn:scim:schemas:extension:wso2:1.0 entry which can be find at the end of
> the scim-schema-extension.config file as shown below.
>
> {
> "attributeURI":"urn:scim:schemas:extension:wso2:1.0",
> "attributeName":"wso2Extension",
> "dataType":"null",
> "multiValued":"false",
> "multiValuedAttributeChildName":"null",
> "description":"SCIM wso2 User Schema Extension",
> "schemaURI":"urn:scim:schemas:extension:wso2:1.0",
> "readOnly":"false",
> "required":"false",
> "caseExact":"false",
> "subAttributes":"employeeNumber costCenter organization division
> department manager askPassword verifyEmail"
> }
>
>
> Also The correct approach to create claim mappings for SCIM extension
> attributes is by configuring external claims for the default SCIM dialect
> (scim:schemas:core:1.0) and not by creating a separate dialect for the
> extension schema (scim:schemas:extension:wso2:1.0:wso2Extension). This is
> already identified in [1] and the relevant documents has been updated.
> Please refer Claim Mapping section in [2]. Also I will create a Doc JIRA to
> improve the documentation with necessary configuration details in [3].
>
>
> [1] https://wso2.org/jira/browse/DOCUMENTATION-4647
> [2] https://docs.wso2.com/display/IS530/Extensible+SCIM+User+
> Schemas+With+WSO2+Identity+Server
> [3] https://docs.wso2.com/display/IS530/Creating+Users+using+
> the+Ask+Password+Option
>
> Thanks,
> Sathya
>
>
>
> On Fri, Nov 3, 2017 at 2:46 PM, Sashika Wijesinghe 
> wrote:
>
>> Hi All,
>>
>> I want to create users with ask password option using SCIM 1.1. I have
>> configured the server as documented in [1].
>>
>> The below curl command is used to create the user. After executing the
>> curl command, the user created successfully but did not receive any email
>> notification for the given email address. This works when I created a user
>> from the management console and SOAP admin service.
>>
>> Do we need any further configurations to get this done with SCIM 1.1?
>>
>> curl -v -k --user admin:admin --data "{"schemas":[],"userName":"nee
>> ls","password":"password","wso2Extension":{"askPassword":"
>> true"},"emails":"sash...@wso2.com"}" --header
>> "Content-Type:application/json" https://localhost:9444/wso2/scim/Users
>>
>> [1] https://docs.wso2.com/display/IS530/Creating+Users+using
>> +the+Ask+Password+Option
>>
>> Thanks
>> Sashika
>>
>>
>>
>>
>> --
>>
>> *Sashika WijesingheSoftware Engineer - QA Team*
>> Mobile : +94 (0) 774537487
>> sash...@wso2.com
>>
>
>
>
> --
> Sathya Bandara
> Software Engineer
> WSO2 Inc. http://wso2.com
> Mobile: (+94) 715 360 421 <+94%2071%20411%205032>
>
> <+94%2071%20411%205032>
>



-- 

*Sashika WijesingheSoftware Engineer - QA Team*
Mobile : +94 (0) 774537487
sash...@wso2.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

Re: [Dev] RabbitMQ connection related errors on WSO2 startup

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

Re: [Dev] [APIM] [C5] package-lock.json files are untracked

Re: [Dev] How to configure SCIM to generate an email when ask password option is provided for user creation

6 matches

Site Navigation

Mail list logo

Footer information