Expected to be relevant for a long period of time (over six months).Only create a new channel if the topic you want to discuss is: New channel conventionsīefore creating a new channel in Rocket.Chat, consider the following questions: You can also create Rocket.Chat channels, for new topics or for your team. Post (appropriate) jokes, share interesting information or articles and get to know other teams working on the platform. Use the #random channel to connect and engage with the platform community on subjects unrelated to the platform. Use the #kudos channel to post a public thank you message or applaud the work of an individual or team. You can also use this channel if you aren’t sure where to post your message. Use the #general channel for anything that might be of interest to the platform community. Vault Secrets Management: #devops-vault.There is a separate channel dedicated to each tool: Platform tool channels are used for discussions about the use and development of various platform tools. We post information about upcoming or ongoing maintenance activities, incidents, outages and changes on the OpenShift platform. Use #devops-alerts to be notified about platform updates. Ask us for help with networking or storage services on the platform.Ask us for help tuning resources for your application.Talk to us about bringing a new product or tool to the platform.Use the #devops-operations channel to connect with the Platform Services team.

Ask for documentation or other support resources.Learn about platform features or tools.Ask for help solving a problem with your application or the platform.Use the #devops-how-to channel to ask non-urgent questions about the BC Gov Private Cloud PaaS or OpenShift platform. government support channels (7-7000, IMB help desks, etc.) should be used for shared infrastructure such as reverse proxies, SiteMinder, firewall rules, etc. Note: The #devops-sos channel is for reporting issues related to the platform. An issue with an OpenShift-hosted tool that is impacting the operations of the production instance of your application.A production problem with your application.Only use the #devops-sos channel for urgent or time-sensitive questions. We monitor the #devops-sos channel during regular business hours. Government Private Cloud PaaS and using OpenShift. Platform service channels are used for questions, updates and information about working in the B.C.

Take some time to explore Rocket.Chat and see if there are any other channels that interest you or that may be relevant to your application. On this page we’ve outlined some of the more frequently used channels, but there are many more channels for you to discover. Learn about some of the Rocket.Chat channels you have access to, and what they’re used for. Any additional InformationĪny help with this matter would be greatly appreciated and I would be happy to provide further details upon is the main communication channel for platform support. Server Setup Informationĭeployed using Helm, with the image rocketchat-3.1.0. Specifically, the above page appears to offer some kind of solution with opening an endpoint for fetching a login token, but that seems to me like overkill for what looks like a relatively simple issue to solve once you have some sort of OAuth running already. I’ve looked at some of the documentation pages such as the Single Sign-on Iframe page, but none of them seem to offer a definitive solution for automatic Keycloak / OAuth login. Meaning that once the user logs into the app, and enters the chat page, the login would happen automatically.

This works well enough, but I would like the login to the Rocket.Chat iframe to be seamless, without having to click on the “Login with Keycloak” button. I’ve recently integrated a Rocket.Chat instance (running on Kubernetes) into an application via an iframe, and used the Keycloak OAuth guide to log the users into the Rocket.Chat instance using the same Keycloak client as the main application (I skipped creating a new client and just used the existing one).

Keycloak rocketchat