Why Are Configured Web Resources Inaccessible?
1. Check whether the server where the connector resides can normally access the backend address.
2. Check whether the backend address path is correct. If the resource is in the root directory, configure the path as the root directory.
3. If the backend service passes through a load balancer or proxy, try configuring the Host in the resource.
What Are the Frontend Address, Backend Address, and Custom Domain Name of a Web Resource? How to Configure Them?
1. The backend address is the address that the connector accesses, which is an address or domain name accessible from the private network or business network.
2. The frontend address is the secure domain name provided by iOA. This domain name is protected by Tencent Cloud WAF. You only need to configure the custom subdomain for this domain name.
3. The custom domain name can be any domain name. You need to point the DNS resolution of the custom domain name to the frontend address.
How to Quickly Access Web Resources from the WeCom Workbench?
2. Configure the business as a Web resource, enable custom domain name configuration, and perform CNAME resolution for the custom domain name on a public DNS resolution platform to point to the frontend domain name of the resource.
3. Authorize resources for users.
4. Add a self-built application in the WeCom admin console. After the trusted domain verification is complete, set the application homepage to the custom domain configured on iOA.
Are There Any Port Restrictions for the Frontend and Backend Addresses of a Web Resource?
1. Web resources do not restrict backend address ports.
2. You can add iOA built-in custom ports to the frontend address port of a Web resource.
Why Is Browser Login Still Required to Access Web Resources When the iOA Client Is Already Installed and Logged In?
Web resources and tunnel resources use different technical solutions for access. Therefore, their access methods are also different, and there is no direct correlation between the two.
Do Web Resources Support Cross-Origin Access?
Yes. If cross-origin access is implemented on the business side, configure the required domain names and ports as Web resources. You can use custom domain names and ports to keep the business address proxied through iOA consistent with the original business address.