Identity Server/API Manager and hidden service provider

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Identity Server/API Manager and hidden service provider

Thomas LEGRAND
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

Can you help me, please?

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Farasath Ahamed
Hi Thomas,

Can you go to the User & Roles --> List --> Roles section.
There you should find a role with the format Application/<Your service Provider Name> (Something like below)

Inline image 1

Thereafter click on Assign User and assign that role to the current logged in user. Once you do that you should be able to see the Service Provider in the management console for the current logged in user.


To give a bit more detail on what happens behind the scenes. 

When you create a Service Provider using the management console, a role in the format Application/<SERVICE_PROVIDER_NAME> gets created and is assigned by default to the user who created the Service Provider. That service provider will only be visible to users who are assigned to  Application/<SERVICE_PROVIDER_NAME> role. So say you created service provider SP1 with user1.

When user2 logs he won't be able to see the Service Provider until the role Application/SP1 is assigned to him.






Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: <a href="tel:%2B94777603866" value="+94713149860" style="font-size:12.8px;color:rgb(17,85,204)" target="_blank">+94777603866
Twitter: @farazath619




On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

Can you help me, please?

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev



_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Rajith Roshan
In reply to this post by Thomas LEGRAND
Hi Thomas,

Instead of configuring IS as key manager , you can use the pre packed IS 5.3.0[1]. Using this pre packed IS is lot easier. 


On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

When you share the database between APIM and IS then data is not stored in the h2 database. It's stored in the AM_DB (for ex : jdbc/WSO2AM_DB which is mentioned in the doc[2]


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Thanks!
Rajith


--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Thomas LEGRAND
In reply to this post by Farasath Ahamed
Hello Farasath,

Thank you for your answer :)

But I connected as admin and it does not appear :(

Images intégrées 1

Regards,

Thomas


2017-06-14 20:10 GMT+02:00 Farasath Ahamed <[hidden email]>:
Hi Thomas,

Can you go to the User & Roles --> List --> Roles section.
There you should find a role with the format Application/<Your service Provider Name> (Something like below)

Inline image 1

Thereafter click on Assign User and assign that role to the current logged in user. Once you do that you should be able to see the Service Provider in the management console for the current logged in user.


To give a bit more detail on what happens behind the scenes. 

When you create a Service Provider using the management console, a role in the format Application/<SERVICE_PROVIDER_NAME> gets created and is assigned by default to the user who created the Service Provider. That service provider will only be visible to users who are assigned to  Application/<SERVICE_PROVIDER_NAME> role. So say you created service provider SP1 with user1.

When user2 logs he won't be able to see the Service Provider until the role Application/SP1 is assigned to him.






Farasath Ahamed
Software Engineer, WSO2 Inc.; http://wso2.com
Mobile: <a href="tel:%2B94777603866" value="+94713149860" style="font-size:12.8px;color:rgb(17,85,204)" target="_blank">+94777603866
Twitter: @farazath619




On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

Can you help me, please?

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Thomas LEGRAND
In reply to this post by Rajith Roshan
Hello Rajith,

Thank you for your answer, too :)

I re-checked my datasources and I have the same URL in both sides (IS and AM) for the WSO2AM_DB, WSO2REG_DB and WSO2UM_DB. So, maybe I did something wrong in another configuration file? Here are my master-datasources.xml for both side, if you want to take a look. I am using H2 in remote mode:

IS datasources:

        <datasource>
            <name>WSO2_CARBON_DB</name>
            <description>The datasource used for registry and user manager</description>
            <jndiConfig>
                <name>jdbc/WSO2CarbonDB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>wso2carbon</username>
                    <password>wso2carbon</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

AM datasources:

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <!--url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url-->
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2UM_DB</name>
            <description>The datasource used for user management</description>
            <jndiConfig>
                <name>jdbc/WSO2UM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2UM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>


And maybe that will fix some problem I have in the store in API manager concerning the error message (Error! You have partially created keys. Please click the Clean Up button and try again). But that is another problem :)

Regards,

Thomas

2017-06-15 7:12 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Instead of configuring IS as key manager , you can use the pre packed IS 5.3.0[1]. Using this pre packed IS is lot easier. 


On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

When you share the database between APIM and IS then data is not stored in the h2 database. It's stored in the AM_DB (for ex : jdbc/WSO2AM_DB which is mentioned in the doc[2]


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Thanks!
Rajith


--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Rajith Roshan
Hi Thomas,

Can you also check the value[1] in identity.xml(repository/conf/identity) of Identity server. It should be as "jdbc/WSO2AM_DB"

<DataSource>
            <!-- Include a data source name (jndiConfigName) from the set of data
                sources defined in master-datasources.xml -->
            <Name>jdbc/WSO2AM_DB</Name>
        </DataSource>

On Thu, Jun 15, 2017 at 2:04 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello Rajith,

Thank you for your answer, too :)

I re-checked my datasources and I have the same URL in both sides (IS and AM) for the WSO2AM_DB, WSO2REG_DB and WSO2UM_DB. So, maybe I did something wrong in another configuration file? Here are my master-datasources.xml for both side, if you want to take a look. I am using H2 in remote mode:

IS datasources:

        <datasource>
            <name>WSO2_CARBON_DB</name>
            <description>The datasource used for registry and user manager</description>
            <jndiConfig>
                <name>jdbc/WSO2CarbonDB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>wso2carbon</username>
                    <password>wso2carbon</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

AM datasources:

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <!--url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url-->
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2UM_DB</name>
            <description>The datasource used for user management</description>
            <jndiConfig>
                <name>jdbc/WSO2UM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2UM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>


And maybe that will fix some problem I have in the store in API manager concerning the error message (Error! You have partially created keys. Please click the Clean Up button and try again). But that is another problem :)

Regards,

Thomas

2017-06-15 7:12 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Instead of configuring IS as key manager , you can use the pre packed IS 5.3.0[1]. Using this pre packed IS is lot easier. 


On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

When you share the database between APIM and IS then data is not stored in the h2 database. It's stored in the AM_DB (for ex : jdbc/WSO2AM_DB which is mentioned in the doc[2]


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Thanks!
Rajith


--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214




--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214

_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Thomas LEGRAND
Hello Rajith,

Thank you very much! That works! I can see the roles and all!

Regards,

Thomas

2017-06-15 10:42 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Can you also check the value[1] in identity.xml(repository/conf/identity) of Identity server. It should be as "jdbc/WSO2AM_DB"

<DataSource>
            <!-- Include a data source name (jndiConfigName) from the set of data
                sources defined in master-datasources.xml -->
            <Name>jdbc/WSO2AM_DB</Name>
        </DataSource>

On Thu, Jun 15, 2017 at 2:04 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello Rajith,

Thank you for your answer, too :)

I re-checked my datasources and I have the same URL in both sides (IS and AM) for the WSO2AM_DB, WSO2REG_DB and WSO2UM_DB. So, maybe I did something wrong in another configuration file? Here are my master-datasources.xml for both side, if you want to take a look. I am using H2 in remote mode:

IS datasources:

        <datasource>
            <name>WSO2_CARBON_DB</name>
            <description>The datasource used for registry and user manager</description>
            <jndiConfig>
                <name>jdbc/WSO2CarbonDB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>wso2carbon</username>
                    <password>wso2carbon</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

AM datasources:

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <!--url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url-->
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2UM_DB</name>
            <description>The datasource used for user management</description>
            <jndiConfig>
                <name>jdbc/WSO2UM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2UM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>


And maybe that will fix some problem I have in the store in API manager concerning the error message (Error! You have partially created keys. Please click the Clean Up button and try again). But that is another problem :)

Regards,

Thomas

2017-06-15 7:12 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Instead of configuring IS as key manager , you can use the pre packed IS 5.3.0[1]. Using this pre packed IS is lot easier. 


On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

When you share the database between APIM and IS then data is not stored in the h2 database. It's stored in the AM_DB (for ex : jdbc/WSO2AM_DB which is mentioned in the doc[2]


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Thanks!
Rajith


--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214




--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Shahintha Ratnasingam

On Thu, Jun 15, 2017 at 2:20 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello Rajith,

Thank you very much! That works! I can see the roles and all!

Regards,

Thomas

2017-06-15 10:42 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Can you also check the value[1] in identity.xml(repository/conf/identity) of Identity server. It should be as "jdbc/WSO2AM_DB"

<DataSource>
            <!-- Include a data source name (jndiConfigName) from the set of data
                sources defined in master-datasources.xml -->
            <Name>jdbc/WSO2AM_DB</Name>
        </DataSource>

On Thu, Jun 15, 2017 at 2:04 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello Rajith,

Thank you for your answer, too :)

I re-checked my datasources and I have the same URL in both sides (IS and AM) for the WSO2AM_DB, WSO2REG_DB and WSO2UM_DB. So, maybe I did something wrong in another configuration file? Here are my master-datasources.xml for both side, if you want to take a look. I am using H2 in remote mode:

IS datasources:

        <datasource>
            <name>WSO2_CARBON_DB</name>
            <description>The datasource used for registry and user manager</description>
            <jndiConfig>
                <name>jdbc/WSO2CarbonDB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>wso2carbon</username>
                    <password>wso2carbon</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

AM datasources:

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <!--url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url-->
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2UM_DB</name>
            <description>The datasource used for user management</description>
            <jndiConfig>
                <name>jdbc/WSO2UM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2UM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>


And maybe that will fix some problem I have in the store in API manager concerning the error message (Error! You have partially created keys. Please click the Clean Up button and try again). But that is another problem :)

Regards,

Thomas

2017-06-15 7:12 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Instead of configuring IS as key manager , you can use the pre packed IS 5.3.0[1]. Using this pre packed IS is lot easier. 


On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

When you share the database between APIM and IS then data is not stored in the h2 database. It's stored in the AM_DB (for ex : jdbc/WSO2AM_DB which is mentioned in the doc[2]


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Thanks!
Rajith


--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214




--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Shahintha Ratnasingam
Software Engineer
M: <a href="tel:+94+77+5915648" style="color:rgb(17,85,204)" target="_blank">+94 77 5915648 | E: [hidden email]
www.wso2telco.com
 
WSO2.Telco (PVT) Ltd.
Bay 9-10-11, Trace Expert City,
Maradana Road,
Colombo 10.
Sri Lanka


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev
Reply | Threaded
Open this post in threaded view
|

Re: Identity Server/API Manager and hidden service provider

Thomas LEGRAND
Hello Shahintha,

I configured the connectivity between the IS and the AM thanks to the document in the API Manager documentation in [1]. So I did not used the ones in the Clustering guides :(



2017-06-15 11:14 GMT+02:00 Shahintha Ratnasingam <[hidden email]>:

On Thu, Jun 15, 2017 at 2:20 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello Rajith,

Thank you very much! That works! I can see the roles and all!

Regards,

Thomas

2017-06-15 10:42 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Can you also check the value[1] in identity.xml(repository/conf/identity) of Identity server. It should be as "jdbc/WSO2AM_DB"

<DataSource>
            <!-- Include a data source name (jndiConfigName) from the set of data
                sources defined in master-datasources.xml -->
            <Name>jdbc/WSO2AM_DB</Name>
        </DataSource>

On Thu, Jun 15, 2017 at 2:04 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello Rajith,

Thank you for your answer, too :)

I re-checked my datasources and I have the same URL in both sides (IS and AM) for the WSO2AM_DB, WSO2REG_DB and WSO2UM_DB. So, maybe I did something wrong in another configuration file? Here are my master-datasources.xml for both side, if you want to take a look. I am using H2 in remote mode:

IS datasources:

        <datasource>
            <name>WSO2_CARBON_DB</name>
            <description>The datasource used for registry and user manager</description>
            <jndiConfig>
                <name>jdbc/WSO2CarbonDB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2CARBON_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>wso2carbon</username>
                    <password>wso2carbon</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>

AM datasources:

        <datasource>
            <name>WSO2AM_DB</name>
            <description>The datasource used for API Manager database</description>
            <jndiConfig>
                <name>jdbc/WSO2AM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
                    <!--url>jdbc:h2:tcp://localhost/D:/ProjetESB/wso2is-5.3.0/repository/database/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url-->
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2AM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2REG_DB</name>
            <description>The datasource used for registry</description>
            <jndiConfig>
                <name>jdbc/WSO2REG_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2REG_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>
        <datasource>
            <name>WSO2UM_DB</name>
            <description>The datasource used for user management</description>
            <jndiConfig>
                <name>jdbc/WSO2UM_DB</name>
            </jndiConfig>
            <definition type="RDBMS">
                <configuration>
<url>jdbc:h2:tcp://localhost/D:/ProjetESB/is_am_db/WSO2UM_DB;DB_CLOSE_ON_EXIT=FALSE</url>
                    <username>apiuser</username>
                    <password>apimanager</password>
                    <driverClassName>org.h2.Driver</driverClassName>
                    <maxActive>50</maxActive>
                    <maxWait>60000</maxWait>
                    <testOnBorrow>true</testOnBorrow>
                    <validationQuery>SELECT 1</validationQuery>
                    <validationInterval>30000</validationInterval>
                </configuration>
            </definition>
        </datasource>


And maybe that will fix some problem I have in the store in API manager concerning the error message (Error! You have partially created keys. Please click the Clean Up button and try again). But that is another problem :)

Regards,

Thomas

2017-06-15 7:12 GMT+02:00 Rajith Roshan <[hidden email]>:
Hi Thomas,

Instead of configuring IS as key manager , you can use the pre packed IS 5.3.0[1]. Using this pre packed IS is lot easier. 


On Wed, Jun 14, 2017 at 6:12 PM, Thomas LEGRAND <[hidden email]> wrote:
Hello everybody,

I have a little problem. I used the Identity Server (IS) in standalone where I configured a service provider and a AD user store. Everything worked perfectly.

Then, I followed the procedure written in the document in [1] to make the API manager use the OAuth token generated by the IS. But, many wild problems appear:

- First, when I connect to the IS, I can see my user store but I can't see my service provider anymore. Where can I find it?
- Then, I try to recreate my service provider with the same name and I have a popup which appears saying:" Error while creating application role: Application/<NAME_HERE> with user admin"
- At last, I try to recreate a service provider with another name and I can configre the SAML thing. So I type the same issuer name and continue the configuration until I click on the update button. And BOOM. Another popup appears telling me that "Could not add Service Provider. You might be entering a duplicate Service Provider". I assume that it is linked to the second point, here :(

I noticed in the default database located in D:\ProjetESB\wso2is-5.3.0\repository\database\WSO2CARBON_DB.h2.db there is a table SP_APP which contained the declaration of my provider. But I don't know where to find its configuration.

When you share the database between APIM and IS then data is not stored in the h2 database. It's stored in the AM_DB (for ex : jdbc/WSO2AM_DB which is mentioned in the doc[2]


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev

Thanks!
Rajith


--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214




--
Rajith Roshan
Software Engineer, WSO2 Inc.
Mobile: <a href="tel:%2B94-71-554-8430" value="+94715548430" target="_blank">+94-717-064-214


_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev




--
Shahintha Ratnasingam
Software Engineer
M: <a href="tel:+94+77+5915648" style="color:rgb(17,85,204)" target="_blank">+94 77 5915648 | E: [hidden email]
www.wso2telco.com
 
WSO2.Telco (PVT) Ltd.
Bay 9-10-11, Trace Expert City,
Maradana Road,
Colombo 10.
Sri Lanka



_______________________________________________
Dev mailing list
[hidden email]
http://wso2.org/cgi-bin/mailman/listinfo/dev