Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add federated idp initiated sso #4936

Open
wants to merge 6 commits into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{% include "../../../../../../includes/guides/authentication/saml/federated-idp-initiated-sso.md" %}
126 changes: 1 addition & 125 deletions en/identity-server/7.0.0/docs/references/default-ports.md
Original file line number Diff line number Diff line change
@@ -1,125 +1 @@
# Default Ports of WSO2 Products

This page describes the default ports that are used for each WSO2 product when the port offset is 0. If you are running multiple WSO2 products on the same server, you must set the `offset` value in the `<IS_HOME>/repository/conf/deployment.toml` file to a different value for each product so that there are no port conflicts.

``` toml
[server]
offset = <PORT_OFFSET_VALUE>
```

For example, if you are running two WSO2 products on the same server, and you set the port offset to `1` in one product and `2` in the second product, the management console port will be changed from the default of `9443` to `9444` in the first product and to `9445` in the second product. See [here](#change-the-offset-for-default-ports) for more information on changing the offset.

## Common ports

The following ports are common to all WSO2 products that provide the given feature. Some features are bundled in the WSO2 Carbon platform itself and therefore are available in all WSO2 products by default.

## Console ports

WSO2 products that provide a WSO2 IS console use the following servlet transport ports:

- `9443` - HTTPS servlet transport (the default URL of the WSO2 IS console is `https://localhost:9443/console`)
- `9763` - HTTP servlet transport


<!-- TODO ## JMX monitoring ports

WSO2 Carbon platform uses TCP ports to monitor a running Carbon instance using a JMX client such as JConsole. By default, JMX is enabled in all products. To disable it, see [Disable JMX for the server]({{base_path}}/deploy/monitor/jmx-based-monitoring/#disable-jmx-for-the-server).

- `11111` - RMIRegistry port. Used to monitor Carbon remotely
- `9999` - RMIServer port. Used along with the RMIRegistry port when Carbon is monitored from a JMX client that is behind a firewall-->


## Clustering ports

To cluster any running Carbon instance, either one of the following ports must be opened.

- `45564` - Opened if the membership scheme is multicast
- `4000` - Opened if the membership scheme is wka

## Random ports

Certain ports are randomly opened during server startup. This is due to specific properties and configurations that become effective when the product is started. Note that the IDs of these random ports will change every time the server is started.

- A random TCP port will open at server startup because of the `-Dcom.sun.management.jmxremote` property set in the server startup script. This property is used for the JMX monitoring facility in JVM.
- A random UDP port is opened at server startup due to the log4j appender `Syslog Appender`, which is configured in the `<IS_HOME>/repository/conf/log4j2.properties` file.

``` xml
# Uncomment the below lines to use the Syslog Appender
#appender.syslog.type = Syslog
#appender.syslog.name = Syslog
#appender.syslog.host = localhost
#appender.syslog.port = 514
#appender.syslog.layout.type = PatternLayout
#appender.syslog.layout.pattern = [%d] [%tenantId] %5p {% raw %}{%c}{% endraw %} - %mm%ex%n
#appender.syslog.filter.threshold.type = ThresholdFilter
#appender.syslog.filter.threshold.level = DEBUG
```

## WSO2 Identity Server ports

WSO2 IS also opens the following additional ports.

- `8000` - `KDCServerPort` : the port on which KDC (Kerberos Key Distribution Center) server runs
- `10500` - `ThriftEntitlementReceivePort`

## Change the offset for default ports

When you run multiple WSO2 products, multiple instances of the same product, or multiple WSO2 product clusters on the same server or virtual machines (VMs), you neeed to change their default ports with an offset value to avoid port conflicts. The default HTTP and HTTPS ports (without offset) of a WSO2 product are 9763 and 9443 respectively.
Port offset defines the number by which all ports defined in the runtime such as the HTTP/S ports will be changed. For example, if the default HTTP port is 9763 and the port offset is 1, the effective HTTP port will change to 9764. For each additional WSO2 product instance, you need to set the port offset to a unique value. The default port offset is 0.

There are two ways to set an offset to a port:

- Pass the port offset to the server during startup. The following command starts the server with the default port incremented by 3.

```
./wso2server.sh -DportOffset=3
```

- Set the `offset` value in the `<IS_HOME>/repository/conf/deployment.toml` file as follows:

``` toml
[server]
offset = <PORT_OFFSET_VALUE>
```

Usually, when you offset the port of the server, all ports it uses are changed automatically. However, there are few exceptions as follows in which you have to change the ports manually according to the offset. The following table indicates the changes that occur when the offset value is modified.

<table>
<colgroup>
<col style="width: 33%" />
<col style="width: 33%" />
<col style="width: 33%" />
</colgroup>
<tbody>
<tr class="odd">
<td><p>WSO2 Server instance</p></td>
<td><p>PortOffset</p></td>
<td><p>Sample Default Port Value</p></td>
</tr>
<tr class="even">
<td><p>WSO2 Product 1</p></td>
<td><p>0</p></td>
<td><p>9443</p></td>
</tr>
<tr class="odd">
<td><p>WSO2 Product 2</p></td>
<td><p>1</p></td>
<td><p>9444</p></td>
</tr>
<tr class="even">
<td><p>WSO2 Product 3</p></td>
<td><p>2</p></td>
<td><p>9445</p></td>
</tr>
<tr class="odd">
<td><p>WSO2 Product 4</p></td>
<td><p>3</p></td>
<td><p>9446</p></td>
</tr>
<tr class="even">
<td><p>WSO2 Product 5</p></td>
<td><p>4</p></td>
<td><p>9447</p></td>
</tr>
</tbody>
</table>
{% include "../../../../includes/references/default-ports.md" %}
1 change: 1 addition & 0 deletions en/identity-server/7.0.0/mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -474,6 +474,7 @@ nav:
- Configure SAML flows:
- Configure SAML flows: guides/authentication/saml/index.md
- Discover SAML endpoints and settings: guides/authentication/saml/discover-saml-configs.md
- Implement federated IdP-initiated SSO: guides/authentication/saml/federated-idp-initiated-sso.md
- Authorization:
- Authorization: guides/authorization/index.md
- API authorization:
Expand Down
Binary file not shown.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{% include "../../../../../../includes/guides/authentication/oidc/oidc-federated-idp-initiated-logout.md" %}
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
{% include "../../../../../../includes/guides/authentication/saml/federated-idp-initiated-sso.md" %}
126 changes: 1 addition & 125 deletions en/identity-server/next/docs/references/default-ports.md
Original file line number Diff line number Diff line change
@@ -1,125 +1 @@
# Default Ports of WSO2 Products

This page describes the default ports that are used for each WSO2 product when the port offset is 0. If you are running multiple WSO2 products on the same server, you must set the `offset` value in the `<IS_HOME>/repository/conf/deployment.toml` file to a different value for each product so that there are no port conflicts.

``` toml
[server]
offset = <PORT_OFFSET_VALUE>
```

For example, if you are running two WSO2 products on the same server, and you set the port offset to `1` in one product and `2` in the second product, the management console port will be changed from the default of `9443` to `9444` in the first product and to `9445` in the second product. See [here](#change-the-offset-for-default-ports) for more information on changing the offset.

## Common ports

The following ports are common to all WSO2 products that provide the given feature. Some features are bundled in the WSO2 Carbon platform itself and therefore are available in all WSO2 products by default.

## Console ports

WSO2 products that provide a WSO2 IS console use the following servlet transport ports:

- `9443` - HTTPS servlet transport (the default URL of the WSO2 IS console is `https://localhost:9443/console`)
- `9763` - HTTP servlet transport


<!-- TODO ## JMX monitoring ports

WSO2 Carbon platform uses TCP ports to monitor a running Carbon instance using a JMX client such as JConsole. By default, JMX is enabled in all products. To disable it, see [Disable JMX for the server]({{base_path}}/deploy/monitor/jmx-based-monitoring/#disable-jmx-for-the-server).

- `11111` - RMIRegistry port. Used to monitor Carbon remotely
- `9999` - RMIServer port. Used along with the RMIRegistry port when Carbon is monitored from a JMX client that is behind a firewall-->


## Clustering ports

To cluster any running Carbon instance, either one of the following ports must be opened.

- `45564` - Opened if the membership scheme is multicast
- `4000` - Opened if the membership scheme is wka

## Random ports

Certain ports are randomly opened during server startup. This is due to specific properties and configurations that become effective when the product is started. Note that the IDs of these random ports will change every time the server is started.

- A random TCP port will open at server startup because of the `-Dcom.sun.management.jmxremote` property set in the server startup script. This property is used for the JMX monitoring facility in JVM.
- A random UDP port is opened at server startup due to the log4j appender `Syslog Appender`, which is configured in the `<IS_HOME>/repository/conf/log4j2.properties` file.

``` xml
# Uncomment the below lines to use the Syslog Appender
#appender.syslog.type = Syslog
#appender.syslog.name = Syslog
#appender.syslog.host = localhost
#appender.syslog.port = 514
#appender.syslog.layout.type = PatternLayout
#appender.syslog.layout.pattern = [%d] [%tenantId] %5p {% raw %}{%c}{% endraw %} - %mm%ex%n
#appender.syslog.filter.threshold.type = ThresholdFilter
#appender.syslog.filter.threshold.level = DEBUG
```

## WSO2 Identity Server ports

WSO2 IS also opens the following additional ports.

- `8000` - `KDCServerPort` : the port on which KDC (Kerberos Key Distribution Center) server runs
- `10500` - `ThriftEntitlementReceivePort`

## Change the offset for default ports

When you run multiple WSO2 products, multiple instances of the same product, or multiple WSO2 product clusters on the same server or virtual machines (VMs), you neeed to change their default ports with an offset value to avoid port conflicts. The default HTTP and HTTPS ports (without offset) of a WSO2 product are 9763 and 9443 respectively.
Port offset defines the number by which all ports defined in the runtime such as the HTTP/S ports will be changed. For example, if the default HTTP port is 9763 and the port offset is 1, the effective HTTP port will change to 9764. For each additional WSO2 product instance, you need to set the port offset to a unique value. The default port offset is 0.

There are two ways to set an offset to a port:

- Pass the port offset to the server during startup. The following command starts the server with the default port incremented by 3.

```
./wso2server.sh -DportOffset=3
```

- Set the `offset` value in the `<IS_HOME>/repository/conf/deployment.toml` file as follows:

``` toml
[server]
offset = <PORT_OFFSET_VALUE>
```

Usually, when you offset the port of the server, all ports it uses are changed automatically. However, there are few exceptions as follows in which you have to change the ports manually according to the offset. The following table indicates the changes that occur when the offset value is modified.

<table>
<colgroup>
<col style="width: 33%" />
<col style="width: 33%" />
<col style="width: 33%" />
</colgroup>
<tbody>
<tr class="odd">
<td><p>WSO2 Server instance</p></td>
<td><p>PortOffset</p></td>
<td><p>Sample Default Port Value</p></td>
</tr>
<tr class="even">
<td><p>WSO2 Product 1</p></td>
<td><p>0</p></td>
<td><p>9443</p></td>
</tr>
<tr class="odd">
<td><p>WSO2 Product 2</p></td>
<td><p>1</p></td>
<td><p>9444</p></td>
</tr>
<tr class="even">
<td><p>WSO2 Product 3</p></td>
<td><p>2</p></td>
<td><p>9445</p></td>
</tr>
<tr class="odd">
<td><p>WSO2 Product 4</p></td>
<td><p>3</p></td>
<td><p>9446</p></td>
</tr>
<tr class="even">
<td><p>WSO2 Product 5</p></td>
<td><p>4</p></td>
<td><p>9447</p></td>
</tr>
</tbody>
</table>
{% include "../../../../includes/references/default-ports.md" %}
1 change: 1 addition & 0 deletions en/identity-server/next/mkdocs.yml
Original file line number Diff line number Diff line change
Expand Up @@ -479,6 +479,7 @@ nav:
- Configure SAML flows:
- Configure SAML flows: guides/authentication/saml/index.md
- Discover SAML endpoints and settings: guides/authentication/saml/discover-saml-configs.md
- Implement federated IdP-initiated SSO: guides/authentication/saml/federated-idp-initiated-sso.md
- Authorization:
- Authorization: guides/authorization/index.md
- API authorization:
Expand Down
Loading