-
Notifications
You must be signed in to change notification settings - Fork 30
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
Agenda for Backstage Community Session (March 16 & 23, 2022) #41
Comments
Proxy - Should we enable it to all existing http requests? what are the disadvantages, when we should not use it? |
There are also security concerns with this approach. If you allow "all" requests to blindly be passed through the proxy plugin a malicious actor could potentially use this to access services/information they should not be able to access normally |
I would be willing to do a quick (~5min) demo of backstage/backstage#9841 |
I can do a small demo (also 5~10 min) of the Periskop plugin we have open-sourced (backstage/backstage#9816). |
[Adopters] Interested in learning what other infosec teams have been leveraging backstage to surface security findings to tech teams (both platform and product engineering teams) |
[Contributors] Frontside team would like to demo the ingestion integration test suite that we created. |
Details
Day 1 (Adopters)
Day 2 (Contributors)
Use this to convert to your timezone
Use this to convert to your timezone
Zoom details
Join Zoom Meeting
https://spotify.zoom.us/j/99236687098
Note: Please sign up on Zoom if you do not have an account. This meeting requires a Zoom account for joining.
In case you face issues joining - feel free to use the
#meetup
channel on Discord.Action Required
[Adopters]
or[Contributors]
in your comment to label them for a specific track.The text was updated successfully, but these errors were encountered: