Commit cdedeca2 authored by Jared Kosanovic's avatar Jared Kosanovic
Browse files

Update email to new service account for service cloud

parent 8d5646e3
......@@ -42,4 +42,4 @@ Access tokens, consumer keys, and consumer keys will also be unaffected by this
The DoIT Integration Platform team is testing the new version of API Manager prior to the upgrade
and will test that the upgrade is successful after WSO2 is done upgrading our environment.
If you have any questions, feel free to [contact us](mailto:doit-integration-platform@office365.wisc.edu).
If you have any questions, feel free to [contact us](mailto:integration-platform@doit.wisc.edu).
......@@ -40,7 +40,7 @@ While this seems attractive to have this kind of mediation in a central location
We recommend handling any mediation in your backend API to better follow the principal of [smart endpoints with dumb pipes](https://medium.com/@nathankpeck/microservice-principles-smart-endpoints-and-dumb-pipes-5691d410700f).
For more information on message mediation in API Cloud, please see [the vendor documentation](https://docs.wso2.com/display/APICloud/Message+Mediation+for+WSO2+API+Cloud), but know that we recommend avoiding this feature if possible.
If you are unsure whether you should use message mediation for your API, feel free to send us an email and we can discuss your specific use case: doit-integration-platform@office365.wisc.edu
If you are unsure whether you should use message mediation for your API, feel free to send us an email and we can discuss your specific use case: integration-platform@doit.wisc.edu
## Detailed and Visible Documentation
......
......@@ -9,7 +9,7 @@ This allows the backend API to know that requests being proxied to it are digita
Mutual TLS provides an additional layer of security beyond allowing the API Cloud IP addresses.
For more information on mutual TLS, [see this article](https://medium.com/sitewards/the-magic-of-tls-x509-and-mutual-authentication-explained-b2162dec4401).
To enable mutual TLS with your API, please send an email to doit-integration-platform@office365.wisc.edu and include the following:
To enable mutual TLS with your API, please send an email to integration-platform@doit.wisc.edu and include the following:
* The name of your API.
* The hostname of your backend API.
......
......@@ -20,7 +20,7 @@ By using OAuth scopes, you can control who is able to use your API *after* subsc
The words “group” and “role” will be used interchangeably for the purposes of this how-to guide and the screens displayed in the API Publisher.
*Note: If you require groups for additional APIs, or require more groups for fine grained access control (e.g. read-only access and read/write access), contact us (doit-integration-platform@office365.wisc.edu) and we can work to facilitate your use case.*
*Note: If you require groups for additional APIs, or require more groups for fine grained access control (e.g. read-only access and read/write access), contact us (integration-platform@doit.wisc.edu) and we can work to facilitate your use case.*
During the third step of publishing or editing an API (the “Manage” step), go to the bottom of the page under the heading “Resources”.
......
......@@ -4,4 +4,4 @@ date: 2019-11-22T13:50:00-06:00
draft: false
---
If you have questions about API Cloud or need advice on your specific use case, please email us: doit-integration-platform@office365.wisc.edu
If you have questions about API Cloud or need advice on your specific use case, please email us: integration-platform@doit.wisc.edu
......@@ -4,7 +4,7 @@ date: 2019-11-22T13:50:00-06:00
draft: false
---
To get access to publish APIs, send an email to doit-integration-platform@office365.wisc.edu and include the following:
To get access to publish APIs, send an email to integration-platform@doit.wisc.edu and include the following:
* Your NetID.
* Your use case for using the API publisher.
......
......@@ -7,4 +7,4 @@ draft: false
The vendor (WSO2) provides [documentation for the entire API Cloud product](https://docs.wso2.com/display/APICloud/WSO2+API+Cloud+Documentation).
Some guides provided by the vendor will instruct users to contact their support to turn on certain features for individual APIs.
The Interoperability team requests that you instead initiate these kind of requests through us so that we can serve as the point of contact for the vendor.
Please send an email to doit-integration-platform@office365.wisc.edu if you encounter something in WSO2’s documentation that requires contacting their support.
Please send an email to integration-platform@doit.wisc.edu if you encounter something in WSO2’s documentation that requires contacting their support.
......@@ -10,4 +10,4 @@ The vendor (WSO2) provides tutorials related to API publishing: https://docs.wso
When you are instructed to go to or the API publisher, use this URL: https://publisher.api.wisc.edu
Some tutorials may instruct you to contact WSO2 directly to enable a certain feature.
Instead, please email us (doit-integration-platform@office365.wisc.edu) so that we can facilitate communication with the vendor.
Instead, please email us (integration-platform@doit.wisc.edu) so that we can facilitate communication with the vendor.
......@@ -19,7 +19,7 @@ Unfortunately, API Cloud does not have a good method to have an application owne
[If you would like to learn more about how to share an application with a group, see this how-to guide](../../how-to-guides/how-to-share-an-application).
Application ownership can also be transferred to another user.
If you would like to transfer application ownership to somebody else on your team, please send an email to doit-integration-platform@office365.wisc.edu and include the following information:
If you would like to transfer application ownership to somebody else on your team, please send an email to integration-platform@doit.wisc.edu and include the following information:
- The name of the application.
- Your NetID, as the current owner of the application.
......
......@@ -108,7 +108,7 @@ This grant type allows someone to exchange a JSON Web Token (JWT) for an access
This grant type is not configured in our instance of WSO2 API Cloud.
For more information on this grant type, [see the specification](https://tools.ietf.org/html/rfc7523).
Please contact us if you require this grant type for your application: doit-integration-platform@office365.wisc.edu
Please contact us if you require this grant type for your application: integration-platform@doit.wisc.edu
### Password (Do Not Use)
......
......@@ -9,7 +9,7 @@ Follow these instructions if you would like to share your application with a gro
1. [Create a group in Manifest using these instructions](https://kb.wisc.edu/iam/page.php?id=25878).
2. Grant Read and View privilieges to your group for our team's group (`uw:org:ais:ais-admins`), so that our team can add your group to our authorization process.
3. Send an email to doit-integration-platform@office365.wisc.edu containing the full name of the Manifest group (e.g. `uw:my:cool:Group`).
3. Send an email to integration-platform@doit.wisc.edu containing the full name of the Manifest group (e.g. `uw:my:cool:Group`).
4. We will map the Manifest group to a group in the API Store. This will allow members of the Manifest group to login and automatically be added to the API Store group. We will respond to you with the name of the WSO2 Group (e.g. Internal/MyCoolGroup).
5. [Follow these instructions to add the group name to the application](https://cloud.docs.wso2.com/en/latest/learn/consume-apis/share-an-application-with-your-team/) that you would like to share.
......@@ -4,7 +4,7 @@ date: 2019-11-22T13:50:00-06:00
draft: false
---
To get access to the API store, send an email to doit-integration-platform@office365.wisc.edu and include the following:
To get access to the API store, send an email to integration-platform@doit.wisc.edu and include the following:
* Your NetID.
* The APIs you're wanting to use.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment