You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Implement new design skeleton
* Update content navigation logic
* Update tab content
* Update to use pythonic operators
* updates requirements
* Update all WorkOS SDK versions in requirements
* Add org selection, table ui, and pagination example to login page
* Update readme to align with new UI
* Update readme to align with new UI
* Remove print statements
* Refactor app navigation
* Remove unused template
* Add pagination table to dsync app home template
Co-authored-by: Adam Wolfman <[email protected]>
Co-authored-by: Adam Wolfman <[email protected]>
Co-authored-by: Adam <[email protected]>
Copy file name to clipboardExpand all lines: python-flask-audit-logs-example/README.md
+5-7Lines changed: 5 additions & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -75,6 +75,7 @@ An example Flask application demonstrating how to use the [WorkOS Python SDK](ht
75
75
```bash
76
76
(env) $ echo$WORKOS_API_KEY
77
77
(env) $ echo$WORKOS_CLIENT_ID
78
+
(env) $ echo$APP_SECRET_KEY
78
79
```
79
80
80
81
9. The final setup step is to start the server.
@@ -106,19 +107,16 @@ You can stop the local Flask server for now by entering `CTRL + c` on the comman
106
107
107
108
## Audit Logs Setup with WorkOS
108
109
109
-
10. Follow the [Audit Logs configuration steps](https://workos.com/docs/audit-logs/emit-an-audit-log-event/sign-in-to-your-workos-dashboard-account-and-configure-audit-log-event-schemas) to set up the following 5 events that are sent with this example:
110
+
10. Follow the [Audit Logs configuration steps](https://workos.com/docs/audit-logs/emit-an-audit-log-event/sign-in-to-your-workos-dashboard-account-and-configure-audit-log-event-schemas) to set up the following 2 events that are sent with this example:
11.Next, take note of the Organization ID for the Org which you will be sending the Audit Log events for. This ID gets entered into the splash page of the example application.
115
+
11.Configure the Admin Portal Redirect URI.
118
116
119
-
12. Once you enter the Organization ID and submit it, you will be brought to the page where you'll be able to send the audit log events that were just configured. You'll also notice that the action of setting the Organization triggered an Audit Log already. Click the buttons to send the respective events.
117
+
Navigate to the Configuration tab in your WorkOS Dshboard. From there click the Admin Portal tab. Click the Edit Admin Portal Redirect Links button and add "http://localhost:5000" to the "When clicking the back navigation, return users to:" input, then click Save Redirect Links.
120
118
121
-
13. To obtain a CSV of the Audit Log events that were sent for the last 30 days, click the "Export Events" button. This will bring you to a new page where you can download the events. Downloading the events is a 2 step process. First you need to create the report by clicking the "Generate CSV" button. Then click the "Access CSV" button to download a CSV of the Audit Log events for the selected Organization for the past 30 days.
119
+
12. To obtain a CSV of the Audit Log events that were sent for the last 30 days, click the "Export Events" tab. This will bring you to a new page where you can download the events. Downloading the events is a 2 step process. First you need to create the report by clicking the "Generate CSV" button. Then click the "Access CSV" button to download a CSV of the Audit Log events for the selected Organization for the past 30 days. You may also adjust the time range using the form inputs.
0 commit comments