From f6b4a2888096b28fb7c0c4f0b7929f4d293f6d17 Mon Sep 17 00:00:00 2001 From: JK Date: Sat, 24 Jan 2026 02:40:46 +0900 Subject: [PATCH] =?UTF-8?q?mdx(en,ja):=20=EC=9D=B4=EB=AF=B8=EC=A7=80=20?= =?UTF-8?q?=ED=83=9C=EA=B7=B8=EC=97=90=20width=20=EC=86=8D=EC=84=B1?= =?UTF-8?q?=EC=9D=84=20=EB=8F=99=EA=B8=B0=ED=99=94=ED=95=A9=EB=8B=88?= =?UTF-8?q?=EB=8B=A4?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - #531 한국어 변경사항(이미지 태그 width 속성)을 영어/일본어에 동기화합니다. - Markdown 이미지 문법을 HTML img 태그로 변환하여 width 속성을 명시합니다. - 기존 영어/일본어 alt 텍스트를 보존합니다. Co-Authored-By: Claude Opus 4.5 --- src/content/en/administrator-manual.mdx | 2 +- .../database-logs/access-control-logs.mdx | 4 +- .../database-logs/account-lock-history.mdx | 4 +- .../audit/database-logs/db-access-history.mdx | 6 +- .../audit/database-logs/dml-snapshots.mdx | 6 +- .../audit/database-logs/policy-audit-logs.mdx | 2 +- .../database-logs/policy-exception-logs.mdx | 2 +- .../audit/database-logs/query-audit.mdx | 6 +- .../audit/database-logs/running-queries.mdx | 6 +- .../audit/general-logs/activity-logs.mdx | 4 +- .../audit/general-logs/admin-role-history.mdx | 2 +- .../audit/general-logs/reverse-tunnels.mdx | 2 +- ...g-with-clusters-through-reverse-tunnel.mdx | 2 +- ...icating-with-db-through-reverse-tunnel.mdx | 2 +- ...ng-with-servers-through-reverse-tunnel.mdx | 2 +- .../general-logs/user-access-history.mdx | 4 +- .../audit/general-logs/workflow-logs.mdx | 2 +- .../kubernetes-role-history.mdx | 8 +-- .../pod-session-recordings.mdx | 14 ++-- .../audit/kubernetes-logs/request-audit.mdx | 10 +-- .../audit/reports/audit-log-export.mdx | 4 +- .../audit/reports/reports.mdx | 8 +-- .../audit/server-logs/access-control-logs.mdx | 6 +- .../server-logs/account-lock-history.mdx | 4 +- .../audit/server-logs/command-audit.mdx | 8 +-- .../server-logs/server-access-history.mdx | 6 +- .../audit/server-logs/server-role-history.mdx | 8 +-- .../audit/server-logs/session-logs.mdx | 10 +-- .../server-logs/session-monitoring-moved.mdx | 4 +- .../web-app-logs/jit-access-control-logs.mdx | 4 +- .../web-app-logs/user-activity-recordings.mdx | 6 +- .../audit/web-app-logs/web-access-history.mdx | 6 +- .../web-app-logs/web-app-role-history.mdx | 6 +- .../audit/web-app-logs/web-event-audit.mdx | 6 +- .../en/administrator-manual/databases.mdx | 2 +- .../connection-management/cloud-providers.mdx | 6 +- .../synchronizing-db-resources-from-aws.mdx | 8 +-- ...onizing-db-resources-from-google-cloud.mdx | 6 +- ...nchronizing-db-resources-from-ms-azure.mdx | 6 +- ...nization-settings-with-dry-run-feature.mdx | 4 +- .../connection-management/db-connections.mdx | 34 +++++----- .../aws-athena-specific-guide.mdx | 2 +- ...rce-configuration-and-log-verification.mdx | 14 ++-- .../documentdb-specific-guide.mdx | 8 +-- ...ery-oauth-authentication-configuration.mdx | 2 +- .../db-connections/mongodb-specific-guide.mdx | 32 ++++----- .../kerberos-configurations.mdx | 8 +-- .../ssh-configurations.mdx | 2 +- .../ssl-configurations.mdx | 2 +- .../databases/dac-general-configurations.mdx | 20 +++--- .../masking-pattern-menu-relocated.mdx | 6 +- .../unmasking-zones.mdx | 6 +- .../databases/db-access-control.mdx | 2 +- .../db-access-control/access-control.mdx | 28 ++++---- .../db-access-control/privilege-type.mdx | 2 +- .../ledger-approval-rules.mdx | 2 +- .../ledger-management/ledger-table-policy.mdx | 4 +- .../databases/monitoring.mdx | 4 +- .../databases/monitoring/proxy-management.mdx | 4 +- .../databases/monitoring/running-queries.mdx | 8 +-- .../databases/new-policy-management.mdx | 2 +- .../new-policy-management/data-paths.mdx | 10 +-- .../new-policy-management/data-policies.mdx | 24 +++---- .../exception-management.mdx | 12 ++-- .../databases/policies/data-access.mdx | 10 +-- .../databases/policies/data-masking.mdx | 6 +- .../databases/policies/masking-pattern.mdx | 6 +- .../databases/policies/policy-exception.mdx | 2 +- .../databases/policies/sensitive-data.mdx | 6 +- .../en/administrator-manual/general.mdx | 2 +- .../general/company-management.mdx | 2 +- .../general/company-management/alerts.mdx | 12 ++-- .../company-management/allowed-zones.mdx | 8 +-- .../general/company-management/channels.mdx | 20 +++--- .../general/company-management/general.mdx | 32 ++++----- .../general/company-management/licenses.mdx | 2 +- .../general/company-management/security.mdx | 22 +++--- .../general/system/api-token.mdx | 10 +-- .../general/system/integrations.mdx | 2 +- .../integrations/identity-providers.mdx | 44 ++++++------ .../integrating-with-aws-sso-saml-20.mdx | 8 +-- ...egrating-google-cloud-api-for-oauth-20.mdx | 10 +-- .../integrations/integrating-with-email.mdx | 10 +-- .../integrating-with-event-callback.mdx | 6 +- .../integrating-with-secret-store.mdx | 12 ++-- .../integrating-with-slack-dm.mdx | 32 ++++----- .../slack-dm-workflow-notification-types.mdx | 10 +-- .../integrations/integrating-with-splunk.mdx | 6 +- .../integrations/integrating-with-syslog.mdx | 4 +- .../integrations/oauth-client-application.mdx | 10 +-- .../general/system/jobs.mdx | 6 +- .../general/system/maintenance.mdx | 2 +- .../general/user-management.mdx | 2 +- .../integrating-with-aws-sso.mdx | 8 +-- .../integrating-with-google-saml.mdx | 22 +++--- .../authentication/integrating-with-ldap.mdx | 14 ++-- .../authentication/integrating-with-okta.mdx | 18 ++--- ...setting-up-multi-factor-authentication.mdx | 6 +- .../general/user-management/groups.mdx | 12 ++-- .../user-management/profile-editor.mdx | 2 +- .../profile-editor/custom-attribute.mdx | 10 +-- .../general/user-management/provisioning.mdx | 4 +- .../provisioning/activating-provisioning.mdx | 2 +- .../okta-provisioning-integration-guide.mdx | 28 ++++---- .../general/user-management/roles.mdx | 16 ++--- .../general/user-management/users.mdx | 32 ++++----- ...n-feature-for-qp-admin-default-account.mdx | 8 +-- .../user-management/users/user-profile.mdx | 14 ++-- .../workflow-management/all-requests.mdx | 4 +- .../workflow-management/approval-rules.mdx | 8 +-- .../workflow-configurations.mdx | 4 +- .../en/administrator-manual/kubernetes.mdx | 2 +- .../connection-management/cloud-providers.mdx | 4 +- ...ronizing-kubernetes-resources-from-aws.mdx | 30 ++++---- .../connection-management/clusters.mdx | 4 +- ...nually-registering-kubernetes-clusters.mdx | 4 +- .../k8s-access-control/access-control.mdx | 12 ++-- ...granting-and-revoking-kubernetes-roles.mdx | 10 +-- .../k8s-access-control/policies.mdx | 22 +++--- ...y-action-configuration-reference-guide.mdx | 2 +- ...kubernetes-policy-ui-code-helper-guide.mdx | 10 +-- .../policies/setting-kubernetes-policies.mdx | 2 +- .../kubernetes/k8s-access-control/roles.mdx | 18 ++--- .../roles/setting-kubernetes-roles.mdx | 10 +-- .../kubernetes/kac-general-configurations.mdx | 2 +- .../en/administrator-manual/servers.mdx | 2 +- .../connection-management/cloud-providers.mdx | 4 +- ...ynchronizing-server-resources-from-aws.mdx | 8 +-- ...chronizing-server-resources-from-azure.mdx | 6 +- ...ynchronizing-server-resources-from-gcp.mdx | 6 +- .../proxyjump-configurations.mdx | 4 +- .../creating-proxyjump.mdx | 2 +- .../server-agents-for-rdp.mdx | 6 +- .../installing-and-removing-server-agent.mdx | 6 +- .../connection-management/server-groups.mdx | 4 +- .../managing-servers-as-groups.mdx | 18 ++--- .../servers/connection-management/servers.mdx | 4 +- ...anually-registering-individual-servers.mdx | 6 +- .../servers/sac-general-configurations.mdx | 8 +-- .../server-access-control/access-control.mdx | 2 +- .../granting-and-revoking-permissions.mdx | 8 +-- .../granting-and-revoking-roles.mdx | 8 +-- .../granting-server-privilege.mdx | 10 +-- .../blocked-accounts.mdx | 2 +- .../command-templates.mdx | 4 +- .../server-access-control/policies.mdx | 18 ++--- .../policies/setting-server-access-policy.mdx | 2 +- .../servers/server-access-control/roles.mdx | 14 ++-- .../account-management.mdx | 8 +-- .../password-provisioning.mdx | 8 +-- .../creating-password-change-job.mdx | 4 +- .../server-account-templates.mdx | 4 +- .../ssh-key-configurations.mdx | 4 +- .../servers/session-monitoring.mdx | 4 +- .../en/administrator-manual/web-apps.mdx | 2 +- .../web-app-configurations.mdx | 2 +- .../connection-management/web-apps.mdx | 8 +-- .../web-apps/wac-quickstart.mdx | 26 +++---- ...0-wac-jit-permission-acquisition-guide.mdx | 12 ++-- ...al-wac-setup-in-web-app-configurations.mdx | 8 +-- ...root-ca-certificate-installation-guide.mdx | 14 ++-- .../web-apps/wac-quickstart/wac-faq.mdx | 4 +- .../wac-troubleshooting-guide.mdx | 12 ++-- .../web-app-access-control/access-control.mdx | 8 +-- .../granting-and-revoking-roles.mdx | 8 +-- .../web-app-access-control/policies.mdx | 20 +++--- .../web-apps/web-app-access-control/roles.mdx | 16 ++--- src/content/en/installation.mdx | 16 ++--- .../container-environment-variables.mdx | 2 +- .../optimizing-dbmaxconnectionsize.mdx | 2 +- .../querypieweburl.mdx | 2 +- .../installation-guide-setupv2sh.mdx | 8 +-- ...nstallation-guide-simple-configuration.mdx | 6 +- .../querypie-acp-community-edition.mdx | 16 ++--- .../mcp-configuration-guide.mdx | 26 +++---- ...rchitecture-and-network-access-control.mdx | 2 +- src/content/en/overview.mdx | 2 +- src/content/en/overview/proxy-management.mdx | 4 +- .../enable-database-proxy.mdx | 4 +- .../overview/system-architecture-overview.mdx | 4 +- .../menu-improvement-guide-9120.mdx | 20 +++--- src/content/en/support/premium-support.mdx | 2 +- .../user-manual/database-access-control.mdx | 4 +- .../connecting-to-custom-data-source.mdx | 14 ++-- .../connecting-to-proxy-without-agent.mdx | 4 +- ...a-google-bigquery-oauth-authentication.mdx | 10 +-- .../connecting-with-web-sql-editor.mdx | 18 ++--- .../setting-default-privilege.mdx | 4 +- .../user-manual/kubernetes-access-control.mdx | 2 +- .../checking-access-permission-list.mdx | 6 +- src/content/en/user-manual/multi-agent.mdx | 68 +++++++++---------- ...ent-linux-installation-and-usage-guide.mdx | 12 ++-- src/content/en/user-manual/my-dashboard.mdx | 14 ++-- .../user-password-reset-via-email.mdx | 14 ++-- src/content/en/user-manual/preferences.mdx | 18 ++--- .../en/user-manual/server-access-control.mdx | 2 +- .../connecting-to-authorized-servers.mdx | 6 +- .../server-access-control/using-web-sftp.mdx | 6 +- .../using-web-terminal.mdx | 6 +- src/content/en/user-manual/user-agent.mdx | 40 +++++------ .../en/user-manual/web-access-control.mdx | 2 +- .../accessing-web-applications-websites.mdx | 4 +- ...ling-root-ca-certificate-and-extension.mdx | 8 +-- src/content/en/user-manual/workflow.mdx | 10 +-- ...atures-proxy-approval-resubmission-etc.mdx | 16 ++--- .../workflow/requesting-access-role.mdx | 14 ++-- .../workflow/requesting-db-access.mdx | 28 ++++---- .../requesting-db-policy-exception.mdx | 10 +-- .../workflow/requesting-ip-registration.mdx | 14 ++-- .../requesting-restricted-data-access.mdx | 10 +-- .../workflow/requesting-server-access.mdx | 16 ++--- .../workflow/requesting-server-privilege.mdx | 22 +++--- .../workflow/requesting-sql-export.mdx | 12 ++-- .../user-manual/workflow/requesting-sql.mdx | 16 ++--- .../using-execution-plan-explain-feature.mdx | 14 ++-- ...uesting-unmasking-mask-removal-request.mdx | 10 +-- src/content/ja/administrator-manual.mdx | 2 +- .../database-logs/access-control-logs.mdx | 4 +- .../database-logs/account-lock-history.mdx | 4 +- .../audit/database-logs/db-access-history.mdx | 6 +- .../audit/database-logs/dml-snapshots.mdx | 6 +- .../audit/database-logs/policy-audit-logs.mdx | 2 +- .../database-logs/policy-exception-logs.mdx | 2 +- .../audit/database-logs/query-audit.mdx | 6 +- .../audit/database-logs/running-queries.mdx | 6 +- .../audit/general-logs/activity-logs.mdx | 4 +- .../audit/general-logs/admin-role-history.mdx | 2 +- .../audit/general-logs/reverse-tunnels.mdx | 2 +- ...g-with-clusters-through-reverse-tunnel.mdx | 2 +- ...icating-with-db-through-reverse-tunnel.mdx | 2 +- ...ng-with-servers-through-reverse-tunnel.mdx | 2 +- .../general-logs/user-access-history.mdx | 4 +- .../audit/general-logs/workflow-logs.mdx | 2 +- .../kubernetes-role-history.mdx | 8 +-- .../pod-session-recordings.mdx | 14 ++-- .../audit/kubernetes-logs/request-audit.mdx | 10 +-- .../audit/reports/audit-log-export.mdx | 4 +- .../audit/reports/reports.mdx | 8 +-- .../audit/server-logs/access-control-logs.mdx | 6 +- .../server-logs/account-lock-history.mdx | 4 +- .../audit/server-logs/command-audit.mdx | 8 +-- .../server-logs/server-access-history.mdx | 6 +- .../audit/server-logs/server-role-history.mdx | 8 +-- .../audit/server-logs/session-logs.mdx | 10 +-- .../server-logs/session-monitoring-moved.mdx | 4 +- .../web-app-logs/jit-access-control-logs.mdx | 4 +- .../web-app-logs/user-activity-recordings.mdx | 6 +- .../audit/web-app-logs/web-access-history.mdx | 6 +- .../web-app-logs/web-app-role-history.mdx | 6 +- .../audit/web-app-logs/web-event-audit.mdx | 6 +- .../ja/administrator-manual/databases.mdx | 2 +- .../connection-management/cloud-providers.mdx | 6 +- .../synchronizing-db-resources-from-aws.mdx | 8 +-- ...onizing-db-resources-from-google-cloud.mdx | 6 +- ...nchronizing-db-resources-from-ms-azure.mdx | 6 +- ...nization-settings-with-dry-run-feature.mdx | 4 +- .../connection-management/db-connections.mdx | 34 +++++----- .../aws-athena-specific-guide.mdx | 2 +- ...rce-configuration-and-log-verification.mdx | 14 ++-- .../documentdb-specific-guide.mdx | 8 +-- ...ery-oauth-authentication-configuration.mdx | 2 +- .../db-connections/mongodb-specific-guide.mdx | 32 ++++----- .../kerberos-configurations.mdx | 8 +-- .../ssh-configurations.mdx | 2 +- .../ssl-configurations.mdx | 2 +- .../databases/dac-general-configurations.mdx | 20 +++--- .../masking-pattern-menu-relocated.mdx | 6 +- .../unmasking-zones.mdx | 6 +- .../databases/db-access-control.mdx | 2 +- .../db-access-control/access-control.mdx | 28 ++++---- .../db-access-control/privilege-type.mdx | 2 +- .../ledger-approval-rules.mdx | 2 +- .../ledger-management/ledger-table-policy.mdx | 4 +- .../databases/monitoring.mdx | 4 +- .../databases/monitoring/proxy-management.mdx | 4 +- .../databases/monitoring/running-queries.mdx | 8 +-- .../databases/new-policy-management.mdx | 2 +- .../new-policy-management/data-paths.mdx | 10 +-- .../new-policy-management/data-policies.mdx | 24 +++---- .../exception-management.mdx | 12 ++-- .../databases/policies/data-access.mdx | 10 +-- .../databases/policies/data-masking.mdx | 6 +- .../databases/policies/masking-pattern.mdx | 6 +- .../databases/policies/policy-exception.mdx | 2 +- .../databases/policies/sensitive-data.mdx | 6 +- .../ja/administrator-manual/general.mdx | 2 +- .../general/company-management.mdx | 2 +- .../general/company-management/alerts.mdx | 12 ++-- .../company-management/allowed-zones.mdx | 8 +-- .../general/company-management/channels.mdx | 20 +++--- .../general/company-management/general.mdx | 32 ++++----- .../general/company-management/licenses.mdx | 2 +- .../general/company-management/security.mdx | 22 +++--- .../general/system/api-token.mdx | 10 +-- .../general/system/integrations.mdx | 2 +- .../integrations/identity-providers.mdx | 44 ++++++------ .../integrating-with-aws-sso-saml-20.mdx | 8 +-- ...egrating-google-cloud-api-for-oauth-20.mdx | 10 +-- .../integrations/integrating-with-email.mdx | 10 +-- .../integrating-with-event-callback.mdx | 6 +- .../integrating-with-secret-store.mdx | 12 ++-- .../integrating-with-slack-dm.mdx | 32 ++++----- .../slack-dm-workflow-notification-types.mdx | 10 +-- .../integrations/integrating-with-splunk.mdx | 6 +- .../integrations/integrating-with-syslog.mdx | 4 +- .../integrations/oauth-client-application.mdx | 10 +-- .../general/system/jobs.mdx | 6 +- .../general/system/maintenance.mdx | 2 +- .../general/user-management.mdx | 2 +- .../integrating-with-aws-sso.mdx | 8 +-- .../integrating-with-google-saml.mdx | 22 +++--- .../authentication/integrating-with-ldap.mdx | 14 ++-- .../authentication/integrating-with-okta.mdx | 18 ++--- ...setting-up-multi-factor-authentication.mdx | 6 +- .../general/user-management/groups.mdx | 12 ++-- .../user-management/profile-editor.mdx | 2 +- .../profile-editor/custom-attribute.mdx | 10 +-- .../general/user-management/provisioning.mdx | 4 +- .../provisioning/activating-provisioning.mdx | 2 +- .../okta-provisioning-integration-guide.mdx | 28 ++++---- .../general/user-management/roles.mdx | 16 ++--- .../general/user-management/users.mdx | 32 ++++----- ...n-feature-for-qp-admin-default-account.mdx | 8 +-- .../user-management/users/user-profile.mdx | 14 ++-- .../workflow-management/all-requests.mdx | 4 +- .../workflow-management/approval-rules.mdx | 8 +-- .../workflow-configurations.mdx | 4 +- .../ja/administrator-manual/kubernetes.mdx | 2 +- .../connection-management/cloud-providers.mdx | 4 +- ...ronizing-kubernetes-resources-from-aws.mdx | 30 ++++---- .../connection-management/clusters.mdx | 4 +- ...nually-registering-kubernetes-clusters.mdx | 4 +- .../k8s-access-control/access-control.mdx | 12 ++-- ...granting-and-revoking-kubernetes-roles.mdx | 10 +-- .../k8s-access-control/policies.mdx | 22 +++--- ...y-action-configuration-reference-guide.mdx | 2 +- ...kubernetes-policy-ui-code-helper-guide.mdx | 10 +-- .../policies/setting-kubernetes-policies.mdx | 2 +- .../kubernetes/k8s-access-control/roles.mdx | 18 ++--- .../roles/setting-kubernetes-roles.mdx | 10 +-- .../kubernetes/kac-general-configurations.mdx | 2 +- .../ja/administrator-manual/servers.mdx | 2 +- .../connection-management/cloud-providers.mdx | 4 +- ...ynchronizing-server-resources-from-aws.mdx | 8 +-- ...chronizing-server-resources-from-azure.mdx | 6 +- ...ynchronizing-server-resources-from-gcp.mdx | 6 +- .../proxyjump-configurations.mdx | 4 +- .../creating-proxyjump.mdx | 2 +- .../server-agents-for-rdp.mdx | 6 +- .../installing-and-removing-server-agent.mdx | 6 +- .../connection-management/server-groups.mdx | 4 +- .../managing-servers-as-groups.mdx | 18 ++--- .../servers/connection-management/servers.mdx | 4 +- ...anually-registering-individual-servers.mdx | 6 +- .../servers/sac-general-configurations.mdx | 8 +-- .../server-access-control/access-control.mdx | 2 +- .../granting-and-revoking-permissions.mdx | 8 +-- .../granting-and-revoking-roles.mdx | 8 +-- .../granting-server-privilege.mdx | 10 +-- .../blocked-accounts.mdx | 2 +- .../command-templates.mdx | 4 +- .../server-access-control/policies.mdx | 18 ++--- .../policies/setting-server-access-policy.mdx | 2 +- .../servers/server-access-control/roles.mdx | 14 ++-- .../account-management.mdx | 8 +-- .../password-provisioning.mdx | 8 +-- .../creating-password-change-job.mdx | 4 +- .../server-account-templates.mdx | 4 +- .../ssh-key-configurations.mdx | 4 +- .../servers/session-monitoring.mdx | 4 +- .../ja/administrator-manual/web-apps.mdx | 2 +- .../web-app-configurations.mdx | 2 +- .../connection-management/web-apps.mdx | 8 +-- .../web-apps/wac-quickstart.mdx | 26 +++---- ...0-wac-jit-permission-acquisition-guide.mdx | 12 ++-- ...al-wac-setup-in-web-app-configurations.mdx | 8 +-- ...root-ca-certificate-installation-guide.mdx | 14 ++-- .../web-apps/wac-quickstart/wac-faq.mdx | 4 +- .../wac-troubleshooting-guide.mdx | 12 ++-- .../web-app-access-control/access-control.mdx | 8 +-- .../granting-and-revoking-roles.mdx | 8 +-- .../web-app-access-control/policies.mdx | 20 +++--- .../web-apps/web-app-access-control/roles.mdx | 16 ++--- src/content/ja/installation.mdx | 16 ++--- .../container-environment-variables.mdx | 2 +- .../optimizing-dbmaxconnectionsize.mdx | 2 +- .../querypieweburl.mdx | 2 +- .../installation-guide-setupv2sh.mdx | 8 +-- ...nstallation-guide-simple-configuration.mdx | 6 +- .../querypie-acp-community-edition.mdx | 16 ++--- .../mcp-configuration-guide.mdx | 26 +++---- ...rchitecture-and-network-access-control.mdx | 2 +- src/content/ja/overview.mdx | 2 +- src/content/ja/overview/proxy-management.mdx | 4 +- .../enable-database-proxy.mdx | 4 +- .../overview/system-architecture-overview.mdx | 4 +- .../menu-improvement-guide-9120.mdx | 20 +++--- src/content/ja/support/premium-support.mdx | 2 +- .../user-manual/database-access-control.mdx | 4 +- .../connecting-to-custom-data-source.mdx | 14 ++-- .../connecting-to-proxy-without-agent.mdx | 4 +- ...a-google-bigquery-oauth-authentication.mdx | 10 +-- .../connecting-with-web-sql-editor.mdx | 18 ++--- .../setting-default-privilege.mdx | 4 +- .../user-manual/kubernetes-access-control.mdx | 2 +- .../checking-access-permission-list.mdx | 6 +- src/content/ja/user-manual/multi-agent.mdx | 68 +++++++++---------- ...ent-linux-installation-and-usage-guide.mdx | 12 ++-- src/content/ja/user-manual/my-dashboard.mdx | 14 ++-- .../user-password-reset-via-email.mdx | 14 ++-- src/content/ja/user-manual/preferences.mdx | 18 ++--- .../ja/user-manual/server-access-control.mdx | 2 +- .../connecting-to-authorized-servers.mdx | 6 +- .../server-access-control/using-web-sftp.mdx | 6 +- .../using-web-terminal.mdx | 6 +- src/content/ja/user-manual/user-agent.mdx | 40 +++++------ .../ja/user-manual/web-access-control.mdx | 2 +- .../accessing-web-applications-websites.mdx | 4 +- ...ling-root-ca-certificate-and-extension.mdx | 8 +-- src/content/ja/user-manual/workflow.mdx | 10 +-- ...atures-proxy-approval-resubmission-etc.mdx | 16 ++--- .../workflow/requesting-access-role.mdx | 14 ++-- .../workflow/requesting-db-access.mdx | 28 ++++---- .../requesting-db-policy-exception.mdx | 10 +-- .../workflow/requesting-ip-registration.mdx | 14 ++-- .../requesting-restricted-data-access.mdx | 10 +-- .../workflow/requesting-server-access.mdx | 16 ++--- .../workflow/requesting-server-privilege.mdx | 22 +++--- .../workflow/requesting-sql-export.mdx | 12 ++-- .../user-manual/workflow/requesting-sql.mdx | 16 ++--- .../using-execution-plan-explain-feature.mdx | 14 ++-- ...uesting-unmasking-mask-removal-request.mdx | 10 +-- 432 files changed, 1988 insertions(+), 1988 deletions(-) diff --git a/src/content/en/administrator-manual.mdx b/src/content/en/administrator-manual.mdx index 63401986..c2e5b4f8 100644 --- a/src/content/en/administrator-manual.mdx +++ b/src/content/en/administrator-manual.mdx @@ -14,7 +14,7 @@ After a successful sign‑in you will land on the user dashboard, and if your ac Click this button to open the Admin page in a new tab.
-![Admin page entry point in the GNB](/administrator-manual/screenshot-20240801-145006.png) +Admin page entry point in the GNB
Admin page entry point in the GNB
diff --git a/src/content/en/administrator-manual/audit/database-logs/access-control-logs.mdx b/src/content/en/administrator-manual/audit/database-logs/access-control-logs.mdx index f512a131..62415481 100644 --- a/src/content/en/administrator-manual/audit/database-logs/access-control-logs.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/access-control-logs.mdx @@ -11,7 +11,7 @@ Records the history of access permission grants and revocations for DB connectio ### Viewing DB Access Control Logs
-![Administrator > Audit > Databases > Access Control Logs](/administrator-manual/audit/database-logs/access-control-logs/image-20240730-072419.png) +Administrator > Audit > Databases > Access Control Logs
Administrator > Audit > Databases > Access Control Logs
@@ -27,7 +27,7 @@ Administrator > Audit > Databases > Access Control Logs 5. **DB Host** : DB host 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240730-073211.png](/administrator-manual/audit/database-logs/access-control-logs/image-20240730-073211.png) + image-20240730-073211.png
1. **Connection Name** : DB connection name 2. **Database Type** : Database type diff --git a/src/content/en/administrator-manual/audit/database-logs/account-lock-history.mdx b/src/content/en/administrator-manual/audit/database-logs/account-lock-history.mdx index e38e33da..cab8b10f 100644 --- a/src/content/en/administrator-manual/audit/database-logs/account-lock-history.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/account-lock-history.mdx @@ -12,7 +12,7 @@ It counts all failed connection attempts such as password input errors and unaut ### Viewing DB Account Lock History
-![Administrator > Audit > Databases > Account Lock History](/administrator-manual/audit/database-logs/account-lock-history/image-20240730-070724.png) +Administrator > Audit > Databases > Account Lock History
Administrator > Audit > Databases > Account Lock History
@@ -23,7 +23,7 @@ Administrator > Audit > Databases > Account Lock History 3. You can search by user name through the search field in the top left of the table. 4. Click the filter button on the right side of the search field to filter by re-specifying the date and time range for **Action At**. Filtering is possible.
- ![image-20240730-071155.png](/administrator-manual/audit/database-logs/account-lock-history/image-20240730-071155.png) + image-20240730-071155.png
1. **Connection Name** : Connected DB connection name 2. **Database Type** : Database type diff --git a/src/content/en/administrator-manual/audit/database-logs/db-access-history.mdx b/src/content/en/administrator-manual/audit/database-logs/db-access-history.mdx index 1ae0b9ba..edbe6f37 100644 --- a/src/content/en/administrator-manual/audit/database-logs/db-access-history.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/db-access-history.mdx @@ -11,7 +11,7 @@ Records the connection and disconnection history of DB connections managed by th ### Viewing DB Access History
-![Administrator > Audit > Databases > DB Access History](/administrator-manual/audit/database-logs/db-access-history/image-20240730-070842.png) +Administrator > Audit > Databases > DB Access History
Administrator > Audit > Databases > DB Access History
@@ -25,7 +25,7 @@ Administrator > Audit > Databases > DB Access History 3. **Client IP** : User IP 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240730-064139.png](/administrator-manual/audit/database-logs/db-access-history/image-20240730-064139.png) + image-20240730-064139.png
1. **Connection Name** : Connected DB connection name 2. **Database Type** : Database type @@ -60,7 +60,7 @@ Administrator > Audit > Databases > DB Access History You can view detailed information by clicking on each row.
-![Administrator > Audit > Databases > DB Access History > DB Access History Details](/administrator-manual/audit/database-logs/db-access-history/image-20240730-065045.png) +Administrator > Audit > Databases > DB Access History > DB Access History Details
Administrator > Audit > Databases > DB Access History > DB Access History Details
diff --git a/src/content/en/administrator-manual/audit/database-logs/dml-snapshots.mdx b/src/content/en/administrator-manual/audit/database-logs/dml-snapshots.mdx index 4f52e991..0be4347a 100644 --- a/src/content/en/administrator-manual/audit/database-logs/dml-snapshots.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/dml-snapshots.mdx @@ -13,7 +13,7 @@ This snapshot stores result information when separate DML Snapshot settings are ### Viewing DML Snapshots
-![Administrator > Audit > Databases > DML Snapshots](/administrator-manual/audit/database-logs/dml-snapshots/image-20240730-094404.png) +Administrator > Audit > Databases > DML Snapshots
Administrator > Audit > Databases > DML Snapshots
@@ -24,7 +24,7 @@ Administrator > Audit > Databases > DML Snapshots 3. You can search by user name through the search field in the top left of the table. 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240730-094947.png](/administrator-manual/audit/database-logs/dml-snapshots/image-20240730-094947.png) + image-20240730-094947.png
1. **Connection Name** : Connected DB connection name 2. **Executed At** : Execution date and time @@ -53,7 +53,7 @@ Administrator > Audit > Databases > DML Snapshots You can view detailed information by clicking on each row.
-![Administrator > Audit > Databases > DML Snapshots > DML Snapshot Details](/administrator-manual/audit/database-logs/dml-snapshots/image-20240730-095257.png) +Administrator > Audit > Databases > DML Snapshots > DML Snapshot Details
Administrator > Audit > Databases > DML Snapshots > DML Snapshot Details
diff --git a/src/content/en/administrator-manual/audit/database-logs/policy-audit-logs.mdx b/src/content/en/administrator-manual/audit/database-logs/policy-audit-logs.mdx index 05cb1bfd..318c54e0 100644 --- a/src/content/en/administrator-manual/audit/database-logs/policy-audit-logs.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/policy-audit-logs.mdx @@ -10,7 +10,7 @@ Records policy creation and status in Audit Logs to allow checking who applied w Records begin and are displayed in the menu when new DAC policies are activated.
-![Audit > Databases > Policy Audit Logs](/administrator-manual/audit/database-logs/policy-audit-logs/image-20250629-174715.png) +Audit > Databases > Policy Audit Logs
Audit > Databases > Policy Audit Logs
diff --git a/src/content/en/administrator-manual/audit/database-logs/policy-exception-logs.mdx b/src/content/en/administrator-manual/audit/database-logs/policy-exception-logs.mdx index 2310bda1..af3f4f6f 100644 --- a/src/content/en/administrator-manual/audit/database-logs/policy-exception-logs.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/policy-exception-logs.mdx @@ -11,7 +11,7 @@ Each time a policy exception is created, modified, deleted, expired, activated, You can view the detailed content of a specific policy exception by clicking on a row in the list.
-![Policy Exception Logs](/administrator-manual/audit/database-logs/policy-exception-logs/image-20250725-132239.png) +Policy Exception Logs
Policy Exception Logs
diff --git a/src/content/en/administrator-manual/audit/database-logs/query-audit.mdx b/src/content/en/administrator-manual/audit/database-logs/query-audit.mdx index 86a0f143..ccf146bc 100644 --- a/src/content/en/administrator-manual/audit/database-logs/query-audit.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/query-audit.mdx @@ -11,7 +11,7 @@ Records the history of completed queries and action executions for DB operations ### Viewing Query Audit
-![Administrator > Audit > Databases > Query Audit](/administrator-manual/audit/database-logs/query-audit/image-20240730-090702.png) +Administrator > Audit > Databases > Query Audit
Administrator > Audit > Databases > Query Audit
@@ -24,7 +24,7 @@ Administrator > Audit > Databases > Query Audit 2. **Table(s)** : Called table name 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240730-091338.png](/administrator-manual/audit/database-logs/query-audit/image-20240730-091338.png) + image-20240730-091338.png
1. **Connection Name** : Connected DB connection name 2. **Database Type** : Database type @@ -81,7 +81,7 @@ Administrator > Audit > Databases > Query Audit You can view detailed information by clicking on each row.
-![Administrator > Audit > Databases > Query Audit > Query Audit Details](/administrator-manual/audit/database-logs/query-audit/image-20240730-091103.png) +Administrator > Audit > Databases > Query Audit > Query Audit Details
Administrator > Audit > Databases > Query Audit > Query Audit Details
diff --git a/src/content/en/administrator-manual/audit/database-logs/running-queries.mdx b/src/content/en/administrator-manual/audit/database-logs/running-queries.mdx index f9499e7a..67dc0d68 100644 --- a/src/content/en/administrator-manual/audit/database-logs/running-queries.mdx +++ b/src/content/en/administrator-manual/audit/database-logs/running-queries.mdx @@ -19,7 +19,7 @@ Please refer to this document for details: Databases > Monitoring > [Runni ### Viewing Running Queries
-![Administrator > Audit > Databases > Running Queries](/administrator-manual/audit/database-logs/running-queries/image-20240730-081612.png) +Administrator > Audit > Databases > Running Queries
Administrator > Audit > Databases > Running Queries
@@ -29,7 +29,7 @@ Administrator > Audit > Databases > Running Queries 2. Logs are displayed in descending order based on the current day. 3. Click the filter button in the top left of the table to filter with AND/OR conditions for the following:
- ![image-20240730-081641.png](/administrator-manual/audit/database-logs/running-queries/image-20240730-081641.png) + image-20240730-081641.png
1. **SQL Type** : SQL statement type 2. **Action At** : Query execution date and time range @@ -66,7 +66,7 @@ Administrator > Audit > Databases > Running Queries You can view detailed information by clicking on each row.
-![Administrator > Audit > Databases > Running Queries > Running Query Details](/administrator-manual/audit/database-logs/running-queries/image-20240730-080947.png) +Administrator > Audit > Databases > Running Queries > Running Query Details
Administrator > Audit > Databases > Running Queries > Running Query Details
diff --git a/src/content/en/administrator-manual/audit/general-logs/activity-logs.mdx b/src/content/en/administrator-manual/audit/general-logs/activity-logs.mdx index 43660cec..1a8d858b 100644 --- a/src/content/en/administrator-manual/audit/general-logs/activity-logs.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/activity-logs.mdx @@ -14,7 +14,7 @@ In Activity logs, you can view the history of resource registration and configur ### Viewing Activity Logs
-![Administrator > Audit > General > Activity Logs](/administrator-manual/audit/general-logs/activity-logs/screenshot-20240722-191106.png) +Administrator > Audit > General > Activity Logs
Administrator > Audit > General > Activity Logs
@@ -35,7 +35,7 @@ Administrator > Audit > General > Activity Logs ### Viewing Activity Logs Details
-![Administrator > Audit > General > Activity Logs > Activity Logs Details](/administrator-manual/audit/general-logs/activity-logs/image-20251009-024238.png) +Administrator > Audit > General > Activity Logs > Activity Logs Details
Administrator > Audit > General > Activity Logs > Activity Logs Details
diff --git a/src/content/en/administrator-manual/audit/general-logs/admin-role-history.mdx b/src/content/en/administrator-manual/audit/general-logs/admin-role-history.mdx index 8178e797..82112d91 100644 --- a/src/content/en/administrator-manual/audit/general-logs/admin-role-history.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/admin-role-history.mdx @@ -14,7 +14,7 @@ When administrator permissions are granted or revoked to specific users in the A ### Viewing Admin Role History
-![Administrator > Audit > General > Admin Role History](/administrator-manual/audit/general-logs/admin-role-history/screenshot-20240722-190405.png) +Administrator > Audit > General > Admin Role History
Administrator > Audit > General > Admin Role History
diff --git a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels.mdx b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels.mdx index f4e7860d..50c84ede 100644 --- a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels.mdx @@ -20,7 +20,7 @@ In 11.4.0, the Reverse Tunnels page that displayed Reverse Tunnel status informa ### Viewing Reverse Tunnels
-![Admin Page > Audit > General > Reverse Tunnels](/administrator-manual/audit/general-logs/reverse-tunnels/image-20250116-123838.png) +Admin Page > Audit > General > Reverse Tunnels
Admin Page > Audit > General > Reverse Tunnels
diff --git a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx index fd6dc1a2..9d4621cc 100644 --- a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx @@ -14,7 +14,7 @@ You can communicate from QueryPie to resources in different Network Zones throug ### Applying Reverse Tunnel to Clusters
-![Administrator > Kubernetes > Connection Management > Clusters > List Details](/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel/image-20250116-124402.png) +Administrator > Kubernetes > Connection Management > Clusters > List Details
Administrator > Kubernetes > Connection Management > Clusters > List Details
diff --git a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx index 60ad0162..c367d58f 100644 --- a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx @@ -14,7 +14,7 @@ You can communicate from QueryPie to resources in different Network Zones throug ### Applying Reverse Tunnels to DB Connection
-![Admin Page > Servers > Connection Management > DB Connections](/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel/image-20250512-122312.png) +Admin Page > Servers > Connection Management > DB Connections
Admin Page > Servers > Connection Management > DB Connections
diff --git a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx index 12cfde3d..d099d044 100644 --- a/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx @@ -14,7 +14,7 @@ You can communicate from QueryPie to resources in different Network Zones throug ### Applying Reverse Tunnels to Servers
-![Admin Page > Servers > Connection Management > Servers](/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel/image-20241209-134405.png) +Admin Page > Servers > Connection Management > Servers
Admin Page > Servers > Connection Management > Servers
diff --git a/src/content/en/administrator-manual/audit/general-logs/user-access-history.mdx b/src/content/en/administrator-manual/audit/general-logs/user-access-history.mdx index 66e87d66..1b7112c7 100644 --- a/src/content/en/administrator-manual/audit/general-logs/user-access-history.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/user-access-history.mdx @@ -12,7 +12,7 @@ You can view all history related to all users' access to the QueryPie system, in ### Viewing User Access History
-![Administrator > Audit > General > User Access History](/administrator-manual/audit/general-logs/user-access-history/image-20240714-063443.png) +Administrator > Audit > General > User Access History
Administrator > Audit > General > User Access History
@@ -37,7 +37,7 @@ Administrator > Audit > General > User Access History You can view detailed information about logs by clicking on individual logs in the User Access History list.
-![Administrator > Audit > General > User Access History > Details](/administrator-manual/audit/general-logs/user-access-history/image-20240721-074544.png) +Administrator > Audit > General > User Access History > Details
Administrator > Audit > General > User Access History > Details
diff --git a/src/content/en/administrator-manual/audit/general-logs/workflow-logs.mdx b/src/content/en/administrator-manual/audit/general-logs/workflow-logs.mdx index c26628cf..32369b33 100644 --- a/src/content/en/administrator-manual/audit/general-logs/workflow-logs.mdx +++ b/src/content/en/administrator-manual/audit/general-logs/workflow-logs.mdx @@ -14,7 +14,7 @@ When users request specific permissions on the Workflow page or approvers approv ### Viewing Workflow Logs
-![Administrator > Audit > General > Workflow Logs](/administrator-manual/audit/general-logs/workflow-logs/image-20241029-052424.png) +Administrator > Audit > General > Workflow Logs
Administrator > Audit > General > Workflow Logs
diff --git a/src/content/en/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx b/src/content/en/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx index 2adfd092..633380b3 100644 --- a/src/content/en/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx +++ b/src/content/en/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx @@ -11,7 +11,7 @@ Records the history of grants and revocations of Kubernetes Roles assigned to Qu ### Viewing Kubernetes Role History
-![Administrator > Audit > Kubernetes > Kubernetes Role History](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-083952.png) +Administrator > Audit > Kubernetes > Kubernetes Role History
Administrator > Audit > Kubernetes > Kubernetes Role History
@@ -25,7 +25,7 @@ Administrator > Audit > Kubernetes > Kubernetes Role History 3. **Role Name** : Kubernetes access permission role name 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240721-084201.png](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-084201.png) + image-20240721-084201.png
1. **Event** : Kubernetes role event type 1. **Role Granted** : Role grant history @@ -53,7 +53,7 @@ Administrator > Audit > Kubernetes > Kubernetes Role History 1. You can view detailed information by clicking on each row.
- ![Administrator > Audit > Kubernetes > Kubernetes Role History > Kubernetes Role History Details](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-084057.png) + Administrator > Audit > Kubernetes > Kubernetes Role History > Kubernetes Role History Details
Administrator > Audit > Kubernetes > Kubernetes Role History > Kubernetes Role History Details
@@ -75,7 +75,7 @@ Administrator > Audit > Kubernetes > Kubernetes Role History 3. **Version** : Version of the assigned policy * Clicking the link displays a popup modal to view the policy code.
- ![image-20240721-084129.png](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-084129.png) + image-20240721-084129.png
1. Shows the Policy Snapshot from when it was granted. * Records remain even if the corresponding Policy is deleted. diff --git a/src/content/en/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx b/src/content/en/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx index 76844297..dcff0f21 100644 --- a/src/content/en/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx +++ b/src/content/en/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx @@ -12,7 +12,7 @@ Administrators can monitor users' execution history in operating container shell ### Viewing Pod Session Recordings
-![Administrator > Audit > Kubernetes > Pod Session Recordings](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082407.png) +Administrator > Audit > Kubernetes > Pod Session Recordings
Administrator > Audit > Kubernetes > Pod Session Recordings
@@ -28,7 +28,7 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 5. **Client Name** : User client name/version (e.g. kubectl/v1.27.3) 4. Click the filter button on the right side of the search field to filter by re-specifying the date and time range for **Action At**.
- ![image-20240721-082446.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082446.png) + image-20240721-082446.png
5. You can refresh the log list through the refresh button in the top right of the table. 6. The table provides the following column information: @@ -48,12 +48,12 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 1. Click the Action At link in each row to play the session recording history. 2. Clicking the Action At link executes a modal and displays a modal showing the initial download process for playback.
- ![image-20240425-022156.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240425-022156.png) + image-20240425-022156.png
3. Depending on whether the recorded file size exceeds 700MB, it displays the playback screen or download button. 1. **Less than 700MB**
- ![image-20240721-082651.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082651.png) + image-20240721-082651.png
1. Basic information is displayed at the top and the Replay playback screen is displayed at the bottom. 1. **Name** : Executor name @@ -65,7 +65,7 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 3. Click the `Close` button to close the window. 2. **700MB or more**
- ![image-20240618-053333.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240618-053333.png) + image-20240618-053333.png
1. Provides a download button along with a message that playback is not possible within the playback screen. 1. The file size exceeds 700MB and the session cannot be played back. @@ -73,8 +73,8 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 2. Click the `Download` button to proceed with the download and create a file locally. 1. When the common option `Export a file with Encryption` located in Administrator > General > Company Management > Security > Others is set to `Required`, an encryption modal appears additionally during the download and the download is executed after the modal.
- ![image-20240721-082733.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082733.png) + image-20240721-082733.png
- ![image-20240425-025317.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240425-025317.png) + image-20240425-025317.png
diff --git a/src/content/en/administrator-manual/audit/kubernetes-logs/request-audit.mdx b/src/content/en/administrator-manual/audit/kubernetes-logs/request-audit.mdx index a48d2182..ef6bb06c 100644 --- a/src/content/en/administrator-manual/audit/kubernetes-logs/request-audit.mdx +++ b/src/content/en/administrator-manual/audit/kubernetes-logs/request-audit.mdx @@ -11,7 +11,7 @@ The QueryPie proxy monitors and records audit logs for each call of API server c ### Viewing Request Audit
-![image-20240721-082824.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240721-082824.png) +image-20240721-082824.png
1. Navigate to the Administrator > Audit > Kubernetes > Request Audit menu. @@ -21,7 +21,7 @@ The QueryPie proxy monitors and records audit logs for each call of API server c 2. **Cluster Name** : Cluster name registered in QueryPie 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240721-082906.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240721-082906.png) + image-20240721-082906.png
1. **Verb** : Specific Kubernetes API action called * `get`, `list`, `watch`, `create`, `update`, `patch`, `delete`, `deletecollection` @@ -55,7 +55,7 @@ The QueryPie proxy monitors and records audit logs for each call of API server c 1. You can view detailed information by clicking on each row.
- ![image-20250116-121412.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20250116-121412.png) + image-20250116-121412.png
1. The top displays information based on basic events: 1. **Result** : API call success/failure status @@ -76,11 +76,11 @@ The QueryPie proxy monitors and records audit logs for each call of API server c 1. This field is viewable in the detail page only for logs where session recording occurred. 2. When executed with Pod exec API, recording for the corresponding session proceeds, and the "Session Recording" text includes a hyperlink.
- ![image-20240512-055657.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240512-055657.png) + image-20240512-055657.png
3. Clicking the link plays the related session recording.
- ![image-20240721-082651.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240721-082651.png) + image-20240721-082651.png
14. The middle section displays information based on API call history: 1. **Verb** : Specific Kubernetes API action called diff --git a/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx b/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx index 0f139fc7..1897460b 100644 --- a/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx +++ b/src/content/en/administrator-manual/audit/reports/audit-log-export.mdx @@ -62,7 +62,7 @@ With the addition of the Audit Log Export feature, the 'Excel File Download' but ### Viewing Audit Log Export List
-![Administrator > Audit > General > Audit Log Export](/administrator-manual/audit/reports/audit-log-export/image-20240714-063656.png) +Administrator > Audit > General > Audit Log Export
Administrator > Audit > General > Audit Log Export
@@ -84,7 +84,7 @@ To start audit log extraction, you need to access the 'Audit > General > A When you click the button, the following screen appears.
-![Administrator > Audit > General > Audit Log Export > Create New Task](/administrator-manual/audit/reports/audit-log-export/screenshot-20250116-131805.png) +Administrator > Audit > General > Audit Log Export > Create New Task
Administrator > Audit > General > Audit Log Export > Create New Task
diff --git a/src/content/en/administrator-manual/audit/reports/reports.mdx b/src/content/en/administrator-manual/audit/reports/reports.mdx index 08832369..b95d38b5 100644 --- a/src/content/en/administrator-manual/audit/reports/reports.mdx +++ b/src/content/en/administrator-manual/audit/reports/reports.mdx @@ -685,7 +685,7 @@ To access the Reports menu, the Report Audit Full Access administrator permissio
-![Administrator > Audit > Reports > Reports](/administrator-manual/audit/reports/reports/screenshot-20241223-112238.png) +Administrator > Audit > Reports > Reports
Administrator > Audit > Reports > Reports
@@ -724,7 +724,7 @@ When you select an item from the report list to view detailed content, a Drawer
-![Administrator > Audit > Reports > Reports > Report Detail](/administrator-manual/audit/reports/reports/screenshot-20241223-112524.png) +Administrator > Audit > Reports > Reports > Report Detail
Administrator > Audit > Reports > Reports > Report Detail
@@ -763,7 +763,7 @@ Click the `+ Create Task` button on the report list screen to enter the report c You can enter task name, report type, scheduling-related content, and specify report output items and filters to apply by section. Click the `+ Add Section` button to add sections.
-![Administrator > Audit > Reports > Reports > Create](/administrator-manual/audit/reports/reports/screenshot-20241209-104337.png) +Administrator > Audit > Reports > Reports > Create
Administrator > Audit > Reports > Reports > Create
@@ -799,7 +799,7 @@ Click the `Save` button to save the report task and return to the list. ### Duplicating Reports**[10.2.2]**
-![Administrator > Audit > Reports > Reports - Duplicate Task](/administrator-manual/audit/reports/reports/screenshot-20241223-104529.png) +Administrator > Audit > Reports > Reports - Duplicate Task
Administrator > Audit > Reports > Reports - Duplicate Task
diff --git a/src/content/en/administrator-manual/audit/server-logs/access-control-logs.mdx b/src/content/en/administrator-manual/audit/server-logs/access-control-logs.mdx index 1af1c7dc..b0c89883 100644 --- a/src/content/en/administrator-manual/audit/server-logs/access-control-logs.mdx +++ b/src/content/en/administrator-manual/audit/server-logs/access-control-logs.mdx @@ -11,7 +11,7 @@ Records the history of grants and revocations of server access Direct Permission ### Viewing Server Access Control Logs
-![Administrator > Audit > Servers > Access Control Logs](/administrator-manual/audit/server-logs/access-control-logs/image-20240728-174950.png) +Administrator > Audit > Servers > Access Control Logs
Administrator > Audit > Servers > Access Control Logs
@@ -28,7 +28,7 @@ Administrator > Audit > Servers > Access Control Logs 6. **Account** : Server account 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240728-174439.png](/administrator-manual/audit/server-logs/access-control-logs/image-20240728-174439.png) + image-20240728-174439.png
1. **Event** : Event type 1. **Access Control Granted** : Permission grant history @@ -61,7 +61,7 @@ Administrator > Audit > Servers > Access Control Logs You can view detailed information by clicking on each row.
-![Administrator > Audit > Servers > Access Control Logs > Access Control Logs Detail](/administrator-manual/audit/server-logs/access-control-logs/image-20240728-175354.png) +Administrator > Audit > Servers > Access Control Logs > Access Control Logs Detail
Administrator > Audit > Servers > Access Control Logs > Access Control Logs Detail
diff --git a/src/content/en/administrator-manual/audit/server-logs/account-lock-history.mdx b/src/content/en/administrator-manual/audit/server-logs/account-lock-history.mdx index d78a8a7f..f39f4ff6 100644 --- a/src/content/en/administrator-manual/audit/server-logs/account-lock-history.mdx +++ b/src/content/en/administrator-manual/audit/server-logs/account-lock-history.mdx @@ -12,7 +12,7 @@ It counts all failed connection attempts such as password input errors and unaut ### Viewing Server Account Lock History
-![Administrator > Audit > Servers > Server Account Lock History](/administrator-manual/audit/server-logs/account-lock-history/image-20240728-175941.png) +Administrator > Audit > Servers > Server Account Lock History
Administrator > Audit > Servers > Server Account Lock History
@@ -28,7 +28,7 @@ Administrator > Audit > Servers > Server Account Lock History 5. **Server Name** : Connected server name 4. Click the filter button on the right side of the search field to filter by re-specifying the date and time range for **Action At**.
- ![image-20240728-180318.png](/administrator-manual/audit/server-logs/account-lock-history/image-20240728-180318.png) + image-20240728-180318.png
1. **Event** : Event type 1. **Account Locked** : User account lock event diff --git a/src/content/en/administrator-manual/audit/server-logs/command-audit.mdx b/src/content/en/administrator-manual/audit/server-logs/command-audit.mdx index ecffcc77..f8b85684 100644 --- a/src/content/en/administrator-manual/audit/server-logs/command-audit.mdx +++ b/src/content/en/administrator-manual/audit/server-logs/command-audit.mdx @@ -14,7 +14,7 @@ For Windows Servers, it records mouse clicks, keyboard inputs, and executed proc ### Viewing Command Audit
-![Administrator > Audit > Servers > Command Audit](/administrator-manual/audit/server-logs/command-audit/image-20240728-171227.png) +Administrator > Audit > Servers > Command Audit
Administrator > Audit > Servers > Command Audit
@@ -29,7 +29,7 @@ Administrator > Audit > Servers > Command Audit * **Role** : Connection role * Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240728-171533.png](/administrator-manual/audit/server-logs/command-audit/image-20240728-171533.png) + image-20240728-171533.png
* **Server OS** : OS of the connected server * **Protocol** : Protocol used for connection @@ -51,7 +51,7 @@ Administrator > Audit > Servers > Command Audit From 11.3.0, when using filters, multiple items can be selected for Action Type.
-![Example of selecting multiple items in Action Type of filter](/administrator-manual/audit/server-logs/command-audit/image-20250930-083734.png) +Example of selecting multiple items in Action Type of filter
Example of selecting multiple items in Action Type of filter
@@ -87,7 +87,7 @@ You can view detailed information by clicking on each row.
-![Administrator > Audit > Servers > Command Audit > Command Audit Details](/administrator-manual/audit/server-logs/command-audit/image-20241209-125101.png) +Administrator > Audit > Servers > Command Audit > Command Audit Details
Administrator > Audit > Servers > Command Audit > Command Audit Details
diff --git a/src/content/en/administrator-manual/audit/server-logs/server-access-history.mdx b/src/content/en/administrator-manual/audit/server-logs/server-access-history.mdx index aba88b22..9227ef8e 100644 --- a/src/content/en/administrator-manual/audit/server-logs/server-access-history.mdx +++ b/src/content/en/administrator-manual/audit/server-logs/server-access-history.mdx @@ -11,7 +11,7 @@ Records the connection history of servers managed by the organization. ### Viewing Server Access History
-![Administrator > Audit > Servers > Server Access History](/administrator-manual/audit/server-logs/server-access-history/image-20240728-165641.png) +Administrator > Audit > Servers > Server Access History
Administrator > Audit > Servers > Server Access History
@@ -30,7 +30,7 @@ Administrator > Audit > Servers > Server Access History 8. **Role** : Connection role 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240728-170045.png](/administrator-manual/audit/server-logs/server-access-history/image-20240728-170045.png) + image-20240728-170045.png
1. **Server OS** : OS of the connected server 2. **Protocol** : Protocol used for connection @@ -63,7 +63,7 @@ You can view detailed information by clicking on each row.
-![Administrator > Audit > Servers > Server Access History > Server Access History Details](/administrator-manual/audit/server-logs/server-access-history/image-20241209-142526.png) +Administrator > Audit > Servers > Server Access History > Server Access History Details
Administrator > Audit > Servers > Server Access History > Server Access History Details
diff --git a/src/content/en/administrator-manual/audit/server-logs/server-role-history.mdx b/src/content/en/administrator-manual/audit/server-logs/server-role-history.mdx index 4335e3c8..a34c6481 100644 --- a/src/content/en/administrator-manual/audit/server-logs/server-role-history.mdx +++ b/src/content/en/administrator-manual/audit/server-logs/server-role-history.mdx @@ -11,7 +11,7 @@ Records the history of grants and revocations of server access Roles assigned to ### Viewing Server Role History
-![Administrator > Audit > Servers > Server Role History](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174347.png) +Administrator > Audit > Servers > Server Role History
Administrator > Audit > Servers > Server Role History
@@ -25,7 +25,7 @@ Administrator > Audit > Servers > Server Role History 3. **Role Name** : Server access permission role name 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20240728-174439.png](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174439.png) + image-20240728-174439.png
1. **Event** : Event type 1. **Role Granted** : Role grant history @@ -51,7 +51,7 @@ Administrator > Audit > Servers > Server Role History You can view detailed information by clicking on each row.
-![Administrator > Audit > Servers > Server Role History > Server Role History Details](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174604.png) +Administrator > Audit > Servers > Server Role History > Server Role History Details
Administrator > Audit > Servers > Server Role History > Server Role History Details
@@ -71,7 +71,7 @@ Administrator > Audit > Servers > Server Role History > Server Role * **Version** : Version of the assigned policy * Clicking the link displays a popup modal to view the policy code.
- ![image-20240728-174822.png](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174822.png) + image-20240728-174822.png
1. Shows the Policy Snapshot from when it was granted. * Records remain even if the corresponding Policy is deleted. diff --git a/src/content/en/administrator-manual/audit/server-logs/session-logs.mdx b/src/content/en/administrator-manual/audit/server-logs/session-logs.mdx index 8e394e99..69fbc128 100644 --- a/src/content/en/administrator-manual/audit/server-logs/session-logs.mdx +++ b/src/content/en/administrator-manual/audit/server-logs/session-logs.mdx @@ -12,7 +12,7 @@ Administrators can monitor users' work execution history within servers through ### Viewing Session Logs
-![Administrator > Audit > Servers > Session Logs](/administrator-manual/audit/server-logs/session-logs/image-20240728-173024.png) +Administrator > Audit > Servers > Session Logs
Administrator > Audit > Servers > Session Logs
@@ -30,7 +30,7 @@ Administrator > Audit > Servers > Session Logs 7. **Client** **Name** : User's connection method 4. Click the filter button on the right side of the search field to filter by re-specifying the date and time range for **Action At**.
- ![image-20240728-173136.png](/administrator-manual/audit/server-logs/session-logs/image-20240728-173136.png) + image-20240728-173136.png
1. **Server OS** : OS of the connected server 2. **Protocol** : Protocol used for connection @@ -63,7 +63,7 @@ Depending on whether the recorded file size exceeds 700MB, it displays the playb 1. **Less than 700MB**
- ![image-20240728-173517.png](/administrator-manual/audit/server-logs/session-logs/image-20240728-173517.png) + image-20240728-173517.png
1. Basic information is displayed at the top and the Replay playback screen is displayed at the bottom. 1. **Name** : Executor name @@ -80,8 +80,8 @@ Depending on whether the recorded file size exceeds 700MB, it displays the playb 2. Click the `Download` button to proceed with the download and create a file locally. 1. When the common option `Export a file with Encryption` located in Administrator > General > Company Management > Security > Others is set to `Required`, an encryption modal appears additionally during the download and the download is executed after the modal.
- ![image-20240721-082733.png](/administrator-manual/audit/server-logs/session-logs/image-20240721-082733.png) + image-20240721-082733.png
- ![image-20240425-025317.png](/administrator-manual/audit/server-logs/session-logs/image-20240425-025317.png) + image-20240425-025317.png
diff --git a/src/content/en/administrator-manual/audit/server-logs/session-monitoring-moved.mdx b/src/content/en/administrator-manual/audit/server-logs/session-monitoring-moved.mdx index 9d55d661..a314c59c 100644 --- a/src/content/en/administrator-manual/audit/server-logs/session-monitoring-moved.mdx +++ b/src/content/en/administrator-manual/audit/server-logs/session-monitoring-moved.mdx @@ -18,7 +18,7 @@ From 11.5.0, Session Monitoring, which was a submenu item under Audit, has been ### Viewing Session Monitoring
-![Administrator > Audit > Servers > Session Monitoring](/administrator-manual/audit/server-logs/session-monitoring-moved/image-20240728-173632.png) +Administrator > Audit > Servers > Session Monitoring
Administrator > Audit > Servers > Session Monitoring
@@ -41,7 +41,7 @@ Administrator > Audit > Servers > Session Monitoring ### Force Terminating Sessions
-![image-20240728-173640.png](/administrator-manual/audit/server-logs/session-monitoring-moved/image-20240728-173640.png) +image-20240728-173640.png
1. Navigate to Administrator > Audit > Servers > Server Monitoring menu. diff --git a/src/content/en/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx b/src/content/en/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx index f86d4e21..43d8051b 100644 --- a/src/content/en/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx +++ b/src/content/en/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx @@ -11,7 +11,7 @@ Records the history of JIT (Just-In-Time) access control logs for web applicatio ### Viewing JIT Access Control Logs
-![Administrator > Audit > Web Apps > JIT Access Control Logs](/administrator-manual/audit/web-app-logs/jit-access-control-logs/image-20250629-174842.png) +Administrator > Audit > Web Apps > JIT Access Control Logs
Administrator > Audit > Web Apps > JIT Access Control Logs
@@ -22,7 +22,7 @@ Administrator > Audit > Web Apps > JIT Access Control Logs 3. You can search with the following conditions through the search field in the top left of the table.
a. **User Name** : User name
b. **User Email** : User email
c. **Web App Name** : Web application name 4. Click the filter button on the right side of the search field to filter with AND conditions for the following:
- ![image-20250629-174904.png](/administrator-manual/audit/web-app-logs/jit-access-control-logs/image-20250629-174904.png) + image-20250629-174904.png
1. **Event** : Event type (JIT Access Granted/JIT Access Revoked) 2. **Action At** : Action occurrence date and time range diff --git a/src/content/en/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx b/src/content/en/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx index b18eb0d8..a008d158 100644 --- a/src/content/en/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx +++ b/src/content/en/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx @@ -13,7 +13,7 @@ Records user activities for web applications managed by the organization. ### Viewing User Activity Recordings
-![Administrator > Audit > Web Apps > User Activity Recordings](/administrator-manual/audit/web-app-logs/user-activity-recordings/image-20250629-175520.png) +Administrator > Audit > Web Apps > User Activity Recordings
Administrator > Audit > Web Apps > User Activity Recordings
@@ -31,7 +31,7 @@ Administrator > Audit > Web Apps > User Activity Recordings 7. **Client Ip** : Client IP address 4. Click the filter button on the right side of the search field to filter with AND conditions for the following:
- ![image-20250629-175600.png](/administrator-manual/audit/web-app-logs/user-activity-recordings/image-20250629-175600.png) + image-20250629-175600.png
**a. Action At** : Action occurrence date and time range @@ -42,7 +42,7 @@ Administrator > Audit > Web Apps > User Activity Recordings You can view detailed information by clicking on each row.
-![Administrator > Audit > Web Apps > User Activity Recordings > User Activity Recordings Details](/administrator-manual/audit/web-app-logs/user-activity-recordings/image-20250629-175637.png) +Administrator > Audit > Web Apps > User Activity Recordings > User Activity Recordings Details
Administrator > Audit > Web Apps > User Activity Recordings > User Activity Recordings Details
diff --git a/src/content/en/administrator-manual/audit/web-app-logs/web-access-history.mdx b/src/content/en/administrator-manual/audit/web-app-logs/web-access-history.mdx index d191849a..9d928cd2 100644 --- a/src/content/en/administrator-manual/audit/web-app-logs/web-access-history.mdx +++ b/src/content/en/administrator-manual/audit/web-app-logs/web-access-history.mdx @@ -11,7 +11,7 @@ Records the role history of web applications managed by the organization. ### Viewing Web Access History
-![Administrator > Audit > Web Apps > Web Access History](/administrator-manual/audit/web-app-logs/web-access-history/image-20250629-171743.png) +Administrator > Audit > Web Apps > Web Access History
Administrator > Audit > Web Apps > Web Access History
@@ -31,7 +31,7 @@ Administrator > Audit > Web Apps > Web Access History 9. **Message** : Message content 4. Click the filter button on the right side of the search field to filter with AND conditions for the following:
- ![image-20250629-171829.png](/administrator-manual/audit/web-app-logs/web-access-history/image-20250629-171829.png) + image-20250629-171829.png
1. **Action Type** : Action type 2. **Action At** : Action occurrence date and time range @@ -41,7 +41,7 @@ Administrator > Audit > Web Apps > Web Access History You can view detailed information by clicking on each row.
-![Administrator > Audit > Web Apps > Web Access History > Web Access History Details](/administrator-manual/audit/web-app-logs/web-access-history/image-20250629-172248.png) +Administrator > Audit > Web Apps > Web Access History > Web Access History Details
Administrator > Audit > Web Apps > Web Access History > Web Access History Details
diff --git a/src/content/en/administrator-manual/audit/web-app-logs/web-app-role-history.mdx b/src/content/en/administrator-manual/audit/web-app-logs/web-app-role-history.mdx index 27deda18..15a073db 100644 --- a/src/content/en/administrator-manual/audit/web-app-logs/web-app-role-history.mdx +++ b/src/content/en/administrator-manual/audit/web-app-logs/web-app-role-history.mdx @@ -11,7 +11,7 @@ Records the history of role grants and revocations for web applications managed ### Viewing Web App Role History
-![Administrator > Audit > Web Apps > Web App Role History](/administrator-manual/audit/web-app-logs/web-app-role-history/Screenshot-2025-06-30-at-2.47.18-PM.png) +Administrator > Audit > Web Apps > Web App Role History
Administrator > Audit > Web Apps > Web App Role History
@@ -22,7 +22,7 @@ Administrator > Audit > Web Apps > Web App Role History 3. You can search with the following conditions through the search field in the top left of the table.
a. User Name : User name
b. User Email : User email
c. Role Name : Role name 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![Screenshot-2025-06-30-at-2.48.27-PM.png](/administrator-manual/audit/web-app-logs/web-app-role-history/Screenshot-2025-06-30-at-2.48.27-PM.png) + Screenshot-2025-06-30-at-2.48.27-PM.png
1. **Event** : Event type 2. **User Type** : User type @@ -44,7 +44,7 @@ Administrator > Audit > Web Apps > Web App Role History You can view detailed information by clicking on each row.
-![Administrator > Audit > Web Apps > Web App Role History > Web App Role History Details](/administrator-manual/audit/web-app-logs/web-app-role-history/Screenshot-2025-06-30-at-2.50.17-PM.png) +Administrator > Audit > Web Apps > Web App Role History > Web App Role History Details
Administrator > Audit > Web Apps > Web App Role History > Web App Role History Details
diff --git a/src/content/en/administrator-manual/audit/web-app-logs/web-event-audit.mdx b/src/content/en/administrator-manual/audit/web-app-logs/web-event-audit.mdx index bd11c650..284c9f1c 100644 --- a/src/content/en/administrator-manual/audit/web-app-logs/web-event-audit.mdx +++ b/src/content/en/administrator-manual/audit/web-app-logs/web-event-audit.mdx @@ -12,7 +12,7 @@ Records the audit history of web application events managed by the organization. ### Viewing Web Event Audit
-![Administrator > Audit > Web Apps > Web Event Audit](/administrator-manual/audit/web-app-logs/web-event-audit/image-20250629-172952.png) +Administrator > Audit > Web Apps > Web Event Audit
Administrator > Audit > Web Apps > Web Event Audit
@@ -33,7 +33,7 @@ Administrator > Audit > Web Apps > Web Event Audit 10. Message : Message content 4. Click the filter button on the right side of the search field to filter with AND/OR conditions for the following:
- ![image-20250629-173418.png](/administrator-manual/audit/web-app-logs/web-event-audit/image-20250629-173418.png) + image-20250629-173418.png
1. Event Type : Event type (Mouse Clicked/Clipboard Copied, etc.) 2. Result : Execution result (Success/Failure) @@ -57,7 +57,7 @@ Administrator > Audit > Web Apps > Web Event Audit You can view detailed information by clicking on each row.
-![Administrator > Audit > Web Apps > Web Event Audit > Event Audit Detail](/administrator-manual/audit/web-app-logs/web-event-audit/image-20250629-172959.png) +Administrator > Audit > Web Apps > Web Event Audit > Event Audit Detail
Administrator > Audit > Web Apps > Web Event Audit > Event Audit Detail
diff --git a/src/content/en/administrator-manual/databases.mdx b/src/content/en/administrator-manual/databases.mdx index 4388e73f..b0bc59d3 100644 --- a/src/content/en/administrator-manual/databases.mdx +++ b/src/content/en/administrator-manual/databases.mdx @@ -7,7 +7,7 @@ import { Callout } from 'nextra/components' # Databases
-![screenshot-20240523-193355.png](/administrator-manual/databases/screenshot-20240523-193355.png) +screenshot-20240523-193355.png
### Overview diff --git a/src/content/en/administrator-manual/databases/connection-management/cloud-providers.mdx b/src/content/en/administrator-manual/databases/connection-management/cloud-providers.mdx index 85f07f11..a81a1156 100644 --- a/src/content/en/administrator-manual/databases/connection-management/cloud-providers.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/cloud-providers.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' QueryPie can integrate DB resources registered with cloud providers and synchronize them periodically.
-![Administrator > Databases > Connection Management > Cloud Providers](/administrator-manual/databases/connection-management/cloud-providers/image-20240714-055708.png) +Administrator > Databases > Connection Management > Cloud Providers
Administrator > Databases > Connection Management > Cloud Providers
@@ -43,7 +43,7 @@ Administrator > Databases > Connection Management > Cloud Providers ### Deleting Cloud Providers
-![image-20241103-065154.png](/administrator-manual/databases/connection-management/cloud-providers/image-20241103-065154.png) +image-20241103-065154.png
1. Navigate to Administrator > Databases > Connection Management > Cloud Providers menu. @@ -65,7 +65,7 @@ To prevent such problems in advance, users can change existing information and t
-![image-20241101-001430.png](/administrator-manual/databases/connection-management/cloud-providers/image-20241101-001430.png) +image-20241101-001430.png
1. Select a specific provider item from the list in Databases > [Connection Management] > Cloud Provider. diff --git a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx index f54b3db1..39c958dd 100644 --- a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx @@ -19,7 +19,7 @@ Search Filter functionality has been added in 11.3.0 to synchronize only resourc
-![Administrator > Databases > Connection Management > Cloud Providers](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20241217-084317.png) +Administrator > Databases > Connection Management > Cloud Providers
Administrator > Databases > Connection Management > Cloud Providers
@@ -50,7 +50,7 @@ Administrator > Databases > Connection Management > Cloud Providers ### Setting Up Authentication Methods by Credential Type
-![Administrator > Databases > Connection Management > Cloud Provider > Create Provider](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20240725-043642.png) +Administrator > Databases > Connection Management > Cloud Provider > Create Provider
Administrator > Databases > Connection Management > Cloud Provider > Create Provider
@@ -65,7 +65,7 @@ Administrator > Databases > Connection Management > Cloud Provider > **Save Credential for Synchronization Option**
-![Save Credential for Synchronization](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20241220-095857.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -91,7 +91,7 @@ Save Credential for Synchronization
-![Administrator > Databases > Connection Management > Cloud Providers > Details](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20241220-100746.png) +Administrator > Databases > Connection Management > Cloud Providers > Details
Administrator > Databases > Connection Management > Cloud Providers > Details
diff --git a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx index c0060389..6dfe380b 100644 --- a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx @@ -18,7 +18,7 @@ Search Filter functionality has been added in 11.3.0 to synchronize only resourc
-![Administrator > Databases > Connection Management > Cloud Providers](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud/image-20241217-123654.png) +Administrator > Databases > Connection Management > Cloud Providers
Administrator > Databases > Connection Management > Cloud Providers
@@ -48,7 +48,7 @@ Administrator > Databases > Connection Management > Cloud Providers **Save Credential for Synchronization Option**
-![Save Credential for Synchronization](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud/image-20241220-094727.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -62,7 +62,7 @@ Save Credential for Synchronization ### Synchronizing and Managing Registered GCP Cloud Provider
-![Administrator > Databases > Connection Management > Cloud Providers > Details](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud/image-20241220-095231.png) +Administrator > Databases > Connection Management > Cloud Providers > Details
Administrator > Databases > Connection Management > Cloud Providers > Details
diff --git a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx index 4b1b440e..4462cb7a 100644 --- a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx @@ -19,7 +19,7 @@ Search Filter functionality has been added in 11.3.0 to synchronize only resourc
-![Administrator > Databases > Connection Management > Cloud Providers > Create Provider](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure/image-20241217-102747.png) +Administrator > Databases > Connection Management > Cloud Providers > Create Provider
Administrator > Databases > Connection Management > Cloud Providers > Create Provider
@@ -53,7 +53,7 @@ Administrator > Databases > Connection Management > Cloud Providers > **Save Credential for Synchronization Option**
-![Save Credential for Synchronization](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure/image-20241221-025943.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -68,7 +68,7 @@ Save Credential for Synchronization ### Synchronizing and Managing Registered Azure Cloud Provider
-![Administrator > Databases > Connection Management > Cloud Providers > Details](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure/image-20241219-060152.png) +Administrator > Databases > Connection Management > Cloud Providers > Details
Administrator > Databases > Connection Management > Cloud Providers > Details
diff --git a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx index cfec754e..83ee95e6 100644 --- a/src/content/en/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx @@ -15,12 +15,12 @@ To prevent such problems in advance, users can change existing information and t 2. Change the setting items you want to change on the detail page, then click the `Dry Run` button in the top right.
-![image-20241101-001430.png](/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature/image-20241101-001430.png) +image-20241101-001430.png
1. Check the "Dry Run" results displayed in the popup window, and if there are any problems, modify the entered content. If there are no problems, click the `Save Changes` button to save the changes.

- ![image-20241101-002631.png](/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature/image-20241101-002631.png) + image-20241101-002631.png
diff --git a/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx b/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx index febcc6ef..b283dbcd 100644 --- a/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/db-connections.mdx @@ -18,7 +18,7 @@ The detailed features described in this document are as follows: Click the `Create Connection` button in the top right of the DB Connections page to enter the manual registration page.
-![Administrator> Databases> Connection Management> DB Connections> Create Connection> Click here](/administrator-manual/databases/connection-management/db-connections/Screenshot-2025-04-10-at-11.33.36-AM.png) +Administrator> Databases> Connection Management> DB Connections> Create Connection> Click here
Administrator> Databases> Connection Management> DB Connections> Create Connection> Click here
@@ -29,7 +29,7 @@ From version 10.2.8, administrators can use the "Supported Features" modal throu This modal is composed of major feature items (Web Editor, Access Control, Audit Log, Privilege Control, Data Policy, Proxy, DML Snapshot, Ledger Management), helping you intuitively check support status for each vendor.
-![Administrator > Databases > Connection Management > DB Connections > Create Connection](/administrator-manual/databases/connection-management/db-connections/image-20240725-062325.png) +Administrator > Databases > Connection Management > DB Connections > Create Connection
Administrator > Databases > Connection Management > DB Connections > Create Connection
@@ -64,7 +64,7 @@ Administrator > Databases > Connection Management > DB Connections > When synchronizing resources through Cloud Provider, if resources are configured as clusters, Cluster mode is activated.
-![Administrator > Databases > Connection Management > DB Connections > List Details](/administrator-manual/databases/connection-management/db-connections/image-20240725-062536.png) +Administrator > Databases > Connection Management > DB Connections > List Details
Administrator > Databases > Connection Management > DB Connections > List Details
@@ -96,7 +96,7 @@ When using Cluster mode, you can manage access permissions in cluster and instan You can view the list of DB connections currently registered in QueryPie in the Databases settings > DB Connections page within the administrator console.
-![Administrator > Databases > Connection Management > DB Connections](/administrator-manual/databases/connection-management/db-connections/image-20240714-055800.png) +Administrator > Databases > Connection Management > DB Connections
Administrator > Databases > Connection Management > DB Connections
@@ -109,7 +109,7 @@ Administrator > Databases > Connection Management > DB Connections * **Favorite View** : Favorite setting status * There is a button for favorite setting on the far right of the table.
- ![Favorite setting button](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-222905.png) + Favorite setting button
Favorite setting button
@@ -128,7 +128,7 @@ Administrator > Databases > Connection Management > DB Connections Click on the item you want to view details for in the DB Connections page to enter the detail page.
-![Administrator > Databases > Connection Management > DB Connections > List Details](/administrator-manual/databases/connection-management/db-connections/Screenshot-2025-04-10-at-11.37.08-AM.png) +Administrator > Databases > Connection Management > DB Connections > List Details
Administrator > Databases > Connection Management > DB Connections > List Details
@@ -141,7 +141,7 @@ From 10.2.8, when viewing details, you can check the list of features supported Click the `Accessible Users` button in the top right of the DB connection detail page to open a Drawer and view the list of users who can access the connection.
-![Administrator > Databases > DB Connections > List Details > Accessible Users](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-223340.png) +Administrator > Databases > DB Connections > List Details > Accessible Users
Administrator > Databases > DB Connections > List Details > Accessible Users
@@ -152,7 +152,7 @@ Administrator > Databases > DB Connections > List Details > Accessib In the Connection Information area of the DB connection detail page, you can view and modify the information entered during creation.
-![Administrator > Databases > DB Connections > List Details > Connection Information](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-223248.png) +Administrator > Databases > DB Connections > List Details > Connection Information
Administrator > Databases > DB Connections > List Details > Connection Information
@@ -203,7 +203,7 @@ Refer to the description for each item. Enter detailed policies to be applied to the DB connection. Save with the `Save Changes` button.
-![Additional Information tab](/administrator-manual/databases/connection-management/db-connections/image-20250825-005925.png) +Additional Information tab
Additional Information tab
@@ -237,7 +237,7 @@ Additional Information tab * When using 3rd party tools (DBeaver, DataGrip, etc.), only SQL Execute items can be forced to require reason input. * Queries sent internally by 3rd party tools (queries that show DB schema in tree structure or display data types in UI) are also detected as SQL Execute and require reason input. Example) Reason input popup appears even when no query is entered immediately after initial connection. In this case, since SQL statement types are not judged, it can cause considerable inconvenience depending on settings. Therefore, the value of the Query Purpose Duration for Agent option in Database > General > Configurations must be adjusted appropriately.
- ![image-20250825-020520.png](/administrator-manual/databases/connection-management/db-connections/image-20250825-020520.png) + image-20250825-020520.png
@@ -247,7 +247,7 @@ Additional Information tab When Proxy Usage is activated, two options are displayed as follows:
-![Proxy Usage options](/administrator-manual/databases/connection-management/db-connections/image-20241222-134235.png) +Proxy Usage options
Proxy Usage options
@@ -266,7 +266,7 @@ When random password usage is difficult, administrators can activate this option Activate SSL or SSH usage through checkboxes and select pre-registered configuration information from the dropdown below. Save with the `Save Changes` button.
-![SSL/SSH Setting tab](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-180833.png) +SSL/SSH Setting tab
SSL/SSH Setting tab
@@ -285,7 +285,7 @@ In the Connection Owner tab, click the `Add Connection Owner` button to specify (Can be specified for users or groups) Save with the `Save Changes` button.
-![Connection Owner tab](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-180851.png) +Connection Owner tab
Connection Owner tab
@@ -301,7 +301,7 @@ In the Tags tab, you can register and manage tags for each DB connection. Click Complete the input and save with the `Save Changes` button.
-![Tags tab](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-231618.png) +Tags tab
Tags tab
@@ -317,7 +317,7 @@ For detailed information, refer to the **DB Connection Security Settings** docum
-![Privilege Setting tab](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-154730.png) +Privilege Setting tab
Privilege Setting tab
@@ -332,7 +332,7 @@ BigQuery, Dynamo, Athena, Impala, Presto, Trino, and Redis vendors do not suppor
-![QueryPie Web > Databases > Connections](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-231958.png) +QueryPie Web > Databases > Connections
QueryPie Web > Databases > Connections
@@ -345,7 +345,7 @@ QueryPie Web > Databases > Connections From 11.3.0, when configuring Advanced privilege, if you do not register a password for a privileged account, the privileged account (administrator account) can manually enter the password when connecting to the target.
-![image-20251013-050034.png](/administrator-manual/databases/connection-management/db-connections/image-20251013-050034.png) +image-20251013-050034.png
To allow manual entry of the DB account password when configuring Advanced privilege, leave the Password field empty and set the "Hide this credential from connection list page" checkbox to unchecked as shown above. diff --git a/src/content/en/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx b/src/content/en/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx index 98354b32..99d96749 100644 --- a/src/content/en/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx @@ -13,7 +13,7 @@ This information must use information registered in IAM. You can check this in AWS IAM > Users page.
-![Screenshot-2025-01-23-at-7.20.29-PM.png](/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide/Screenshot-2025-01-23-at-7.20.29-PM.png) +Screenshot-2025-01-23-at-7.20.29-PM.png
### Cloud Provider diff --git a/src/content/en/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx b/src/content/en/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx index f6c2a5ee..0e54dc27 100644 --- a/src/content/en/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx @@ -30,19 +30,19 @@ This feature was added in version 10.2.6. * Select Admin > Databases > Connection Management > DB Connections. * Click the `+ Create Connection` button.
- ![Screenshot-2025-03-05-at-10.10.11-AM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-10.10.11-AM.png) + Screenshot-2025-03-05-at-10.10.11-AM.png
2. **Create Custom Data Source** * Click the Custom Data Source icon.
- ![Screenshot-2025-03-05-at-10.11.42-AM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-10.11.42-AM.png) + Screenshot-2025-03-05-at-10.11.42-AM.png
* When creating, the following warning message is displayed:
**Restrictions:** * Only TCP access control is available; Privilege control and Query Audit are not supported. * Access is only possible through a proxy; it cannot be accessed via the web editor. * Enter the following connection information according to your desired settings. ****
- ![Screenshot-2025-03-05-at-12.02.22-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-12.02.22-PM.png) + Screenshot-2025-03-05-at-12.02.22-PM.png
* Connection Name (Required) : Enter connection name * Host (Required) : Host address of the target data source @@ -61,13 +61,13 @@ This feature was added in version 10.2.6. * You can change desired items and add Tags. * After modification, click the `Save Changes` button in the top right to save changes.
- ![Screenshot-2025-03-05-at-6.43.08-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-6.43.08-PM.png) + Screenshot-2025-03-05-at-6.43.08-PM.png
* **Deletion** * Select the checkbox on the left of the connection you want to delete from the DB Connections list, then click the `Delete` button. * After the "Are you sure you want to delete" message appears, click the `OK` button to delete the connection.
- ![Screenshot-2025-03-05-at-6.54.56-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-6.54.56-PM.png) + Screenshot-2025-03-05-at-6.54.56-PM.png
#### Setting Up Access Control @@ -82,7 +82,7 @@ This feature was added in version 10.2.6. * You can set an expiration date when granting. * After selection is complete, click the `Grant` button to grant permissions.
- ![Screenshot-2025-03-05-at-1.59.53-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-1.59.53-PM.png) + Screenshot-2025-03-05-at-1.59.53-PM.png
@@ -92,7 +92,7 @@ This feature was added in version 10.2.6. * Select Admin > Databases > DB Access Control > Access Control > User. * Select the connection to revoke permissions from on the Detail page, then click the `Revoke` button.
- ![Screenshot-2025-03-05-at-3.18.12-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-3.18.12-PM.png) + Screenshot-2025-03-05-at-3.18.12-PM.png
#### Checking Audit Logs diff --git a/src/content/en/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx b/src/content/en/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx index 42fa9bf3..e6dc7010 100644 --- a/src/content/en/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx @@ -19,7 +19,7 @@ After cloud synchronization, as shown in the screen below, it shows multi-host c It is recommended to use Cluster endpoint rather than connecting through instance endpoint.
-![image-20240122-102557.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240122-102557.png) +image-20240122-102557.png
### Using Amazon DocumentDB TLS(SSL) @@ -36,7 +36,7 @@ AWS provides two types: [global bundle certificate](https://docs.aws.amazon.com/ 2. Navigate to Databases > Connection Management > SSL Configurations menu in QueryPie administrator console.
-![image-20240730-112808.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240730-112808.png) +image-20240730-112808.png
1. Click the `Create SSL` button in the top right. @@ -46,7 +46,7 @@ AWS provides two types: [global bundle certificate](https://docs.aws.amazon.com/ 5. Click the `Save` button to save the settings.
-![image-20240220-225433.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240220-225433.png) +image-20240220-225433.png
#### Mapping Certificate to DocumentDB @@ -57,7 +57,7 @@ AWS provides two types: [global bundle certificate](https://docs.aws.amazon.com/ 4. Check the `Use SSL` checkbox to enable it, then select the setting name registered in the previous step (Registering CA Bundle Certificate) from **SSL Configurations**.
-![image-20240220-230604.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240220-230604.png) +image-20240220-230604.png
1. Click the `Save Changes` button in the top right to save the settings. diff --git a/src/content/en/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx b/src/content/en/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx index ae2b9cd4..090ec67b 100644 --- a/src/content/en/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx @@ -20,7 +20,7 @@ For Google Cloud API Integration setup, please refer to this document: [Integrat Both cloud-synchronized connections and manually created connections can select "Using Google User Account (OAuth 2.0)" as the Authentication Method.
-![Specify Authentication Method when creating a new BigQuery connection](/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration/image-20250116-112226.png) +Specify Authentication Method when creating a new BigQuery connection
Specify Authentication Method when creating a new BigQuery connection
diff --git a/src/content/en/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx b/src/content/en/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx index 80f01b61..74e6aa9e 100644 --- a/src/content/en/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx @@ -54,7 +54,7 @@ Nevertheless, if direct access to subordinate hosts in +srv connection environme #### 2. Creating MongoDB Connections
-![Administrator > Databases > Connection Management > DB Connections > Create Connection](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-113638.png) +Administrator > Databases > Connection Management > DB Connections > Create Connection
Administrator > Databases > Connection Management > DB Connections > Create Connection
@@ -69,7 +69,7 @@ Administrator > Databases > Connection Management > DB Connections > ##### < Standard Connection >
-![image-20240730-114050.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114050.png) +image-20240730-114050.png
1. Set appropriate network zone settings in Allowed Zone. @@ -86,7 +86,7 @@ Administrator > Databases > Connection Management > DB Connections > 3. Expose is an option that can determine the exposure of individual instances in connection information.
**To use multi-host functionality, instances must be in expose state, so be sure to activate the** `Expose` **option.**
-![image-20240730-114226.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114226.png) +image-20240730-114226.png
1. Authentication DB : Enter the value of Authentication DB (authSource). @@ -104,7 +104,7 @@ ______ ##### < +srv Connection >
-![image-20240730-114540.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114540.png) +image-20240730-114540.png
1. Set appropriate network zone settings in Allowed Zone. @@ -130,7 +130,7 @@ Sharded Cluster has the same setup method as Replica Set, only the Connection St Replica Set requires replicaSet=[replica set name] option, but Sharded Cluster doesn't need this option.
-![image-20240730-114833.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114833.png) +image-20240730-114833.png
##### < Standard Connection > @@ -168,7 +168,7 @@ As mentioned above, when using QueryPie's SQL editor for connection, tls=true is When using Proxy, SSL settings are required in QueryPie separately from TLS settings in SQL clients like DataGrip.
Refer to [SSL Configurations](../ssl-configurations) for setup and reflect in the connection's SSL settings.
-![image-20240731-050745.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240731-050745.png) +image-20240731-050745.png
@@ -189,7 +189,7 @@ Please check the links below for initial policy creation. #### Registering Rules in Masking Policy
-![Administrator > Databases > Policies > Data Masking > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-115120.png) +Administrator > Databases > Policies > Data Masking > Add Rule List
Administrator > Databases > Policies > Data Masking > Add Rule List
@@ -215,7 +215,7 @@ Administrator > Databases > Policies > Data Masking > Add Rule List After creating a policy, register the data path to which the policy will be applied as rules.
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-115402.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
@@ -254,7 +254,7 @@ Examples of MongoDB data to which policies are applied are as follows: ##### Case 1. item Attribute Access Restriction
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-115402.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
@@ -263,7 +263,7 @@ Administrator > Databases > Policies > Data Access > Add Rule List When setting access restriction policy for one attribute, enter the corresponding item in the "Column Name" field and click the `OK` button.
-![image-20240730-120312.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120312.png) +image-20240730-120312.png
As shown in the screenshot above, you can see that the value of the item("T_PWD") attribute is displayed as "Restricted Column". @@ -273,14 +273,14 @@ As shown in the screenshot above, you can see that the value of the item("T_PWD" When setting access restriction policy for the h attribute under size, enter `$.size.h` in the "Column Name" field and click the `OK` button.
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120011.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
-![image-20240730-120215.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120215.png) +image-20240730-120215.png
As shown in the screenshot above, you can see that the value of the h attribute under size is displayed as "Restricted Column". @@ -290,14 +290,14 @@ As shown in the screenshot above, you can see that the value of the h attribute When setting access restriction policy for all attributes under size, enter `$.size` in the "Column Name" field and click the `OK` button.
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120351.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
-![image-20240730-120421.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120421.png) +image-20240730-120421.png
As shown in the screenshot above, you can see that the values of all attributes under size are displayed as "Restricted Column". @@ -307,14 +307,14 @@ As shown in the screenshot above, you can see that the values of all attributes When setting access restriction policy for the 2nd value in the tags attribute list, enter `$.tags[1]` in the "Column Name" field and click the `OK` button.
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120507.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
-![image-20240730-120544.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120544.png) +image-20240730-120544.png
As shown in the screenshot above, you can see that the 2nd value of the tags attribute is displayed as "Restricted Column". diff --git a/src/content/en/administrator-manual/databases/connection-management/kerberos-configurations.mdx b/src/content/en/administrator-manual/databases/connection-management/kerberos-configurations.mdx index 9238c27b..d94401c8 100644 --- a/src/content/en/administrator-manual/databases/connection-management/kerberos-configurations.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/kerberos-configurations.mdx @@ -15,7 +15,7 @@ Click the `Create Keytab` button in the top right of the Kerberos Configurations Upload the keytab file, enter the name of the Kerberos configuration, and click the `Save` button to save.
-![Administrator > Databases > Connection Management > Kerberos Configurations > Create Keytab](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111247.png) +Administrator > Databases > Connection Management > Kerberos Configurations > Create Keytab
Administrator > Databases > Connection Management > Kerberos Configurations > Create Keytab
@@ -27,7 +27,7 @@ Administrator > Databases > Connection Management > Kerberos Configurat You can view the list of registered keytabs on the Kerberos Configurations page.
-![Administrator > Databases > Connection Management > Kerberos Configurations](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111157.png) +Administrator > Databases > Connection Management > Kerberos Configurations
Administrator > Databases > Connection Management > Kerberos Configurations
@@ -40,7 +40,7 @@ Select the item you want to delete from the list in the Kerberos Configurations Click the button and click the `Delete` button in the confirmation modal to complete deletion.
-![Administrator > Databases > Connection Management > Kerberos Configurations > Delete Keytab](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111214.png) +Administrator > Databases > Connection Management > Kerberos Configurations > Delete Keytab
Administrator > Databases > Connection Management > Kerberos Configurations > Delete Keytab
@@ -53,7 +53,7 @@ Click the `⚙️` button in the top right of the Kerberos Configurations page t Click the `Save` button to save the changes.
-![Administrator > Databases > Connection Management > Kerberos Configurations > Kerberos Configuration Setting](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111234.png) +Administrator > Databases > Connection Management > Kerberos Configurations > Kerberos Configuration Setting
Administrator > Databases > Connection Management > Kerberos Configurations > Kerberos Configuration Setting
diff --git a/src/content/en/administrator-manual/databases/connection-management/ssh-configurations.mdx b/src/content/en/administrator-manual/databases/connection-management/ssh-configurations.mdx index ccd060ff..3888271a 100644 --- a/src/content/en/administrator-manual/databases/connection-management/ssh-configurations.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/ssh-configurations.mdx @@ -9,7 +9,7 @@ title: 'SSH Configurations' SSH Configurations is a page for managing SSH tunneling information to use when connecting DB connections.
-![Administrator > Databases > Connection Management > SSH Configuration > Create SSH Configuration](/administrator-manual/databases/connection-management/ssh-configurations/screenshot-20240730-230232.png) +Administrator > Databases > Connection Management > SSH Configuration > Create SSH Configuration
Administrator > Databases > Connection Management > SSH Configuration > Create SSH Configuration
diff --git a/src/content/en/administrator-manual/databases/connection-management/ssl-configurations.mdx b/src/content/en/administrator-manual/databases/connection-management/ssl-configurations.mdx index 0dbf6063..8700c4bf 100644 --- a/src/content/en/administrator-manual/databases/connection-management/ssl-configurations.mdx +++ b/src/content/en/administrator-manual/databases/connection-management/ssl-configurations.mdx @@ -9,7 +9,7 @@ title: 'SSL Configurations' Register SSL configuration information to use when connecting to DB connections on the SSL Configurations page.
-![Administrator > Databases > Connection Management > SSL Configuration > Create SSL](/administrator-manual/databases/connection-management/ssl-configurations/screenshot-20240730-230107.png) +Administrator > Databases > Connection Management > SSL Configuration > Create SSL
Administrator > Databases > Connection Management > SSL Configuration > Create SSL
diff --git a/src/content/en/administrator-manual/databases/dac-general-configurations.mdx b/src/content/en/administrator-manual/databases/dac-general-configurations.mdx index b3184f53..8d0cd1be 100644 --- a/src/content/en/administrator-manual/databases/dac-general-configurations.mdx +++ b/src/content/en/administrator-manual/databases/dac-general-configurations.mdx @@ -19,7 +19,7 @@ From 11.5.0, email notification functionality has been added to notify users bef Manages settings applied to DB access control.
-![image-20251218-083844.png](/administrator-manual/databases/dac-general-configurations/image-20251218-083844.png) +image-20251218-083844.png
@@ -29,10 +29,10 @@ Manages settings applied to DB access control.
By default, query sharing settings are off, and clicking the `Query Sharing Setting` button opens a settings modal. When Query Sharing option is set to On, additional input fields are displayed.
-![screenshot-20240726-145003.png](/administrator-manual/databases/dac-general-configurations/screenshot-20240726-145003.png) +screenshot-20240726-145003.png
-![screenshot-20240726-145650.png](/administrator-manual/databases/dac-general-configurations/screenshot-20240726-145650.png) +screenshot-20240726-145650.png
* **Git Repository URL** : Git Repository URL to send queries to @@ -76,12 +76,12 @@ ______ * Cannot set expiration dates exceeding the specified period when requesting DB Access Request * **Notification of Access Expiration** : Enables email notifications to users before privilege expiration (Privilege Expiration, Policy Exception Expiration).
- ![image-20251218-084512.png](/administrator-manual/databases/dac-general-configurations/image-20251218-084512.png) + image-20251218-084512.png
* **Display the first 10 rows in Query Audit** : Query Audit SELECT statement execution result display method setting (Default: Off, when set to On, only the first 10 rows are displayed instead of showing all results)
-![Query Audit Detail](/administrator-manual/databases/dac-general-configurations/screenshot-20231210-174400.png) +Query Audit Detail
Query Audit Detail
@@ -98,7 +98,7 @@ Query Audit Detail * Allowed User : Specify users allowed to execute the corresponding statement (multiple selection possible, group-level specification not possible) * Queries containing entered Restricted Statement are blocked when executed
- ![image-20240326-011036.png](/administrator-manual/databases/dac-general-configurations/image-20240326-011036.png) + image-20240326-011036.png
@@ -109,7 +109,7 @@ Do not enter queries that should be allowed for execution by certain users. * **Justification Length** : When "User Action Purpose Required" option is activated in Connection settings or reason input is forced by Ledger table management policies, reason input must be made through Web Editor or Agent. Administrators specify the minimum and maximum values for the number of characters entered in the input field. * The minimum input value is 1 and the maximum value is 1000.
- ![image-20250824-233845.png](/administrator-manual/databases/dac-general-configurations/image-20250824-233845.png) + image-20250824-233845.png
* **Query Annotation** : Automatically records annotations specified by administrators when performing queries. When the feature is activated, annotations are recorded using the following 3 templates. As of 10.4.0, limited to Redshift support. * User Name: `{{userName}}` : Display Name of the user who performed the query. @@ -117,7 +117,7 @@ Do not enter queries that should be allowed for execution by certain users. * Execute From: `{{executedFrom}}` : The means by which the query was performed. As of 10.4.0, only Web Editor is recorded.
-![Query Audit](/administrator-manual/databases/dac-general-configurations/image-20250627-140103.png) +Query Audit
Query Audit
@@ -128,7 +128,7 @@ Query Audit * **Member based Connection Filtering :** Feature to filter and show only specified connections instead of showing all connections for specific users or groups in DB Access Request forms in Workflow. * Only connections registered as connection members in the connection detail screen are exposed in Workflow DB Access Request.
- ![Assign specific users or groups to Connection Member in the detail screen of a specific connection in Databases > Connection Management > DB Connections](/administrator-manual/databases/dac-general-configurations/image-20250627-141133.png) + Assign specific users or groups to Connection Member in the detail screen of a specific connection in Databases > Connection Management > DB Connections
Assign specific users or groups to Connection Member in the detail screen of a specific connection in Databases > Connection Management > DB Connections
@@ -146,7 +146,7 @@ For detailed configuration methods, please refer to [DB Connections](connection- * Minimum: 1 hour
-![image-20251009-150744.png](/administrator-manual/databases/dac-general-configurations/image-20251009-150744.png) +image-20251009-150744.png
diff --git a/src/content/en/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx b/src/content/en/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx index c12d4521..c237d3da 100644 --- a/src/content/en/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx +++ b/src/content/en/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx @@ -22,7 +22,7 @@ On the Masking Pattern page, you can view the registered masking patterns. (searchable by pattern name)
-![Administrator > Databases > General > Masking Pattern](/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated/image-20250826-005621.png) +Administrator > Databases > General > Masking Pattern
Administrator > Databases > General > Masking Pattern
@@ -34,7 +34,7 @@ Administrator > Databases > General > Masking Pattern Click an item in the table to open a drawer where you can view, edit, or delete its details.
-![Administrator > Databases > General > Masking Pattern > Details](/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated/image-20250826-005930.png) +Administrator > Databases > General > Masking Pattern > Details
Administrator > Databases > General > Masking Pattern > Details
@@ -60,7 +60,7 @@ Click the `Create Pattern` button to open a modal. Enter all the required information and click the `Save` button to save.
-![Create Pattern](/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated/screenshot-20240731-174002.png) +Create Pattern
Create Pattern
diff --git a/src/content/en/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx b/src/content/en/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx index 2e69ebae..49572492 100644 --- a/src/content/en/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx +++ b/src/content/en/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx @@ -20,12 +20,12 @@ To set up Unmasking Zones, you first need [Allowed Zones setup](../../general/co 2. Change the Unmasking Zones radio button to `On` and click the `+ Add Configuration` button.
-![image-20250515-085639.png](/administrator-manual/databases/dac-general-configurations/unmasking-zones/image-20250515-085639.png) +image-20250515-085639.png
1. Select the Allowed Zone name you want to add to Unmasking Zones.
- ![Add Allowed Zone](/administrator-manual/databases/dac-general-configurations/unmasking-zones/image-20250411-080251.png) + Add Allowed Zone
Add Allowed Zone
@@ -43,7 +43,7 @@ When modified, it is also reflected in Unmasking Zones settings. 1. Select the specific Allowed zone you want to remove from the Unmasking zones list and click the `Delete` button.
- ![image-20250411-080409.png](/administrator-manual/databases/dac-general-configurations/unmasking-zones/image-20250411-080409.png) + image-20250411-080409.png
2. Click the `Save Changes` button to save the changes. diff --git a/src/content/en/administrator-manual/databases/db-access-control.mdx b/src/content/en/administrator-manual/databases/db-access-control.mdx index def6db12..cd67ce51 100644 --- a/src/content/en/administrator-manual/databases/db-access-control.mdx +++ b/src/content/en/administrator-manual/databases/db-access-control.mdx @@ -11,7 +11,7 @@ Only authenticated users can access databases that have been granted access perm From initial QueryPie user authentication to database access, important data can be safely protected through IP range control, long-term inactivity control, time and day-of-week control, table/column query restrictions, etc. All changes to security policies are immediately applied to user sessions, enabling real-time enforcement of updated measures.
-![Administrator > Databases > DB Access Control > Access Control](/administrator-manual/databases/db-access-control/screenshot-20240731-113229.png) +Administrator > Databases > DB Access Control > Access Control
Administrator > Databases > DB Access Control > Access Control
diff --git a/src/content/en/administrator-manual/databases/db-access-control/access-control.mdx b/src/content/en/administrator-manual/databases/db-access-control/access-control.mdx index 3ed139bd..2f6bb782 100644 --- a/src/content/en/administrator-manual/databases/db-access-control/access-control.mdx +++ b/src/content/en/administrator-manual/databases/db-access-control/access-control.mdx @@ -22,7 +22,7 @@ On the Access Control page, you can view the DB privileges and administrator rol * Locked Accounts: You can check users who are locked due to account lock conditions and unlock them.
-![Administrator > Databases > DB Access Control > Access Control](/administrator-manual/databases/db-access-control/access-control/image-20251209-061107.png) +Administrator > Databases > DB Access Control > Access Control
Administrator > Databases > DB Access Control > Access Control
@@ -34,7 +34,7 @@ Administrator > Databases > DB Access Control > Access Control Clicking on a specific user or group row in the Groups / Users tab list on the Access Control page opens a detail screen where you can view information about targets that have been granted privileges.
-![Access control detail page for a specific user](/administrator-manual/databases/db-access-control/access-control/image-20251218-085542.png) +Access control detail page for a specific user
Access control detail page for a specific user
@@ -73,16 +73,16 @@ Access control detail page for a specific user 3. Click the `Grant Privilege` button. 4. In the popup window, select Host from Access Control Level. (Default: Host)
- ![image-20251218-095117.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-095117.png) + image-20251218-095117.png
5. Select the connection to grant privileges to and choose a specific privilege type.
- ![image-20251218-095406.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-095406.png) + image-20251218-095406.png
6. If necessary, set the privilege expiration date in Expiration date and click the `Grant` button. 7. You can also select multiple connections to grant privileges in bulk.
- ![image-20251218-095817.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-095817.png) + image-20251218-095817.png
@@ -100,20 +100,20 @@ DBMS that support Schema Level privilege assignment as of version 11.5.0:
At 3. Click the `Grant Privilege` button. 4. In the popup window, select Schema(Logical DB) from Access Control Level. (Default: Host)
- ![image-20251218-104148.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-104148.png) + image-20251218-104148.png
5. Select the target connection from the Connections item. Schema level does not support multiple settings for multiple connections at once. When you select a connection, you can see that SELECT privilege is automatically granted to schemas that require select privilege in the privilege item on the right. Administrators can remove this item, but if they do, errors may occur when querying schema structure in Web editor or proxy, so it is recommended not to remove this item if possible. 6. Click the `Add Item` button to specify a specific schema (logical DB) to assign privileges to.
A row is added below where you can add targets. For DBMS with schema structure (Oracle, Postgres, etc.), you must enter the target name in the format `{database name}`.`{schema name}`. For DBMS without schema structure like MySQL, enter only the logical DB name.
- Oracle example: ORCLDB.TESTUSER
- PostgreSQL example: testdb.test_schema
- MySQL example: sakila
- ![image-20251218-105030.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-105030.png) + image-20251218-105030.png
7. To assign privileges, first select the desired privilege type from the Host Level Privilege item at the top right of the popup window. (Schema level privileges can only be granted within the scope of host level privileges. For example, if you select Read/Write as Host Level Privilege, you can grant SELECT, INSERT, etc. within that scope, but if you select Read-Only as Host Level Privilege, you can only specify SELECT.)
- ![image-20251218-110506.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-110506.png) + image-20251218-110506.png
8. Host Level Others and Host Level Functions displayed below are read-only. To modify them, you must modify the corresponding Privilege Type in the Databases > DB Access Control > Privilege Type menu. They are used to check upper-level information because Schema Level privileges are dependent on the properties of Host Level Privileges.
- ![image-20251218-111204.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-111204.png) + image-20251218-111204.png
9. If necessary, set the privilege expiration date in Expiration date and click the `Grant` button. @@ -134,7 +134,7 @@ When a user has multiple privileges granted through both individual user privile ### Revoking Access Control Privileges
-![Administrator > Databases > DB Access Control > Access Control > Details](/administrator-manual/databases/db-access-control/access-control/image-20241209-122146.png) +Administrator > Databases > DB Access Control > Access Control > Details
Administrator > Databases > DB Access Control > Access Control > Details
@@ -168,7 +168,7 @@ Users whose privileges have been revoked can no longer access the connection, an ### Unlocking Locked Connection Accounts
-![Administrator > Databases > DB Access Control > Access Control > Locked Account](/administrator-manual/databases/db-access-control/access-control/image-20241209-123011.png) +Administrator > Databases > DB Access Control > Access Control > Locked Account
Administrator > Databases > DB Access Control > Access Control > Locked Account
@@ -179,7 +179,7 @@ Administrator > Databases > DB Access Control > Access Control > Loc 3. Select the item you want to unlock and click `Unlock` on the right to unlock the connection.
-![image-20241209-123358.png](/administrator-manual/databases/db-access-control/access-control/image-20241209-123358.png) +image-20241209-123358.png
1. Connection lock and unlock history can be checked in the Audit > Databases > Account Lock History menu. @@ -189,7 +189,7 @@ Administrator > Databases > DB Access Control > Access Control > Loc **Access Control with Table Tags**

When New DAC Policy Management is enabled in Databases > General > Configurations,
-![image-20250703-050924.png](/administrator-manual/databases/db-access-control/access-control/image-20250703-050924.png) +image-20250703-050924.png
In Access Control, you can control access to only tables with specific tags for connections that specific users are allowed to access. @@ -205,7 +205,7 @@ If the conditions are met, you can set it up as follows: 2. In the detailed screen, select Tag-based table access as the Access Type and add tags. You can only select and use existing tags (tags assigned to tables).
-![image-20250703-051824.png](/administrator-manual/databases/db-access-control/access-control/image-20250703-051824.png) +image-20250703-051824.png
If you enable the Tag-based table access feature but don't register any tags, you won't be able to access any tables in that connection.
diff --git a/src/content/en/administrator-manual/databases/db-access-control/privilege-type.mdx b/src/content/en/administrator-manual/databases/db-access-control/privilege-type.mdx index 64590381..1c5b1b12 100644 --- a/src/content/en/administrator-manual/databases/db-access-control/privilege-type.mdx +++ b/src/content/en/administrator-manual/databases/db-access-control/privilege-type.mdx @@ -20,7 +20,7 @@ When creating privileges, MySQL-based SET, SHOW, DESCRIBE, and USE statements ar
-![Administrator > Databases > DB Access Control > Privilege Type](/administrator-manual/databases/db-access-control/privilege-type/image-20240725-071543.png) +Administrator > Databases > DB Access Control > Privilege Type
Administrator > Databases > DB Access Control > Privilege Type
diff --git a/src/content/en/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx b/src/content/en/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx index 2b08ce5e..36027ac9 100644 --- a/src/content/en/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx +++ b/src/content/en/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx @@ -21,7 +21,7 @@ Please contact the QueryPie customer support team to use this feature. You can separately create and manage approval rules to be enforced when applying ledger table policies.
-![Administrator > Databases > Ledger Management > Ledger Approval Rules](/administrator-manual/databases/ledger-management/ledger-approval-rules/Screenshot-2024-12-18-at-11.52.33-AM.png) +Administrator > Databases > Ledger Management > Ledger Approval Rules
Administrator > Databases > Ledger Management > Ledger Approval Rules
diff --git a/src/content/en/administrator-manual/databases/ledger-management/ledger-table-policy.mdx b/src/content/en/administrator-manual/databases/ledger-management/ledger-table-policy.mdx index 7eee5f65..6d826bf9 100644 --- a/src/content/en/administrator-manual/databases/ledger-management/ledger-table-policy.mdx +++ b/src/content/en/administrator-manual/databases/ledger-management/ledger-table-policy.mdx @@ -25,7 +25,7 @@ You can create policies by DB connection and map approval rules to tables to be After setup, when users attempt to execute modification queries such as UPDATE or export data on the corresponding table, you can configure SQL Requests through the corresponding approval rules.
-![Administrator > Databases > Ledger Management > Ledger Table Policy](/administrator-manual/databases/ledger-management/ledger-table-policy/Screenshot-2024-12-18-at-11.46.38-AM.png) +Administrator > Databases > Ledger Management > Ledger Table Policy
Administrator > Databases > Ledger Management > Ledger Table Policy
@@ -41,7 +41,7 @@ Administrator > Databases > Ledger Management > Ledger Table Policy You can verify that policies have been created in the Ledger Table Policy list by DB connection.
-![Administrator > Databases > Ledger Management > Ledger Table Policy > Details](/administrator-manual/databases/ledger-management/ledger-table-policy/Screenshot-2024-12-18-at-11.47.34-AM.png) +Administrator > Databases > Ledger Management > Ledger Table Policy > Details
Administrator > Databases > Ledger Management > Ledger Table Policy > Details
diff --git a/src/content/en/administrator-manual/databases/monitoring.mdx b/src/content/en/administrator-manual/databases/monitoring.mdx index 66fa101b..599cf8ae 100644 --- a/src/content/en/administrator-manual/databases/monitoring.mdx +++ b/src/content/en/administrator-manual/databases/monitoring.mdx @@ -24,14 +24,14 @@ Proxy Management had session force functionality from before and has only been m
-![Databases > Monitoring > Running Queries](/administrator-manual/databases/monitoring/image-20250512-101633.png) +Databases > Monitoring > Running Queries
Databases > Monitoring > Running Queries
-![Databases > Monitoring > Proxy Management](/administrator-manual/databases/monitoring/image-20250512-104613.png) +Databases > Monitoring > Proxy Management
Databases > Monitoring > Proxy Management
diff --git a/src/content/en/administrator-manual/databases/monitoring/proxy-management.mdx b/src/content/en/administrator-manual/databases/monitoring/proxy-management.mdx index 4f6afbe6..e8ee7ac8 100644 --- a/src/content/en/administrator-manual/databases/monitoring/proxy-management.mdx +++ b/src/content/en/administrator-manual/databases/monitoring/proxy-management.mdx @@ -20,7 +20,7 @@ When users execute queries via 3rd-party tools such as DataGrip or DBeaver, you * **Status**: Displays whether it is active.
-![Administrator > Databases > Monitoring > Proxy Management](/administrator-manual/databases/monitoring/proxy-management/image-20250512-113752.png) +Administrator > Databases > Monitoring > Proxy Management
Administrator > Databases > Monitoring > Proxy Management
@@ -38,7 +38,7 @@ By default, the proxy usage option is disabled. Enable proxy usage for connections you want to allow access to.
-![image-20240725-070857.png](/administrator-manual/databases/monitoring/proxy-management/image-20240725-070857.png) +image-20240725-070857.png
1. Navigate to the DB Connections menu from the Database settings menu. diff --git a/src/content/en/administrator-manual/databases/monitoring/running-queries.mdx b/src/content/en/administrator-manual/databases/monitoring/running-queries.mdx index 56682d3e..4b0d8225 100644 --- a/src/content/en/administrator-manual/databases/monitoring/running-queries.mdx +++ b/src/content/en/administrator-manual/databases/monitoring/running-queries.mdx @@ -14,7 +14,7 @@ You can check whether executed queries are from Web Editor or executed through W ### Viewing Running Queries
-![Databases > Monitoring > Running Queries](/administrator-manual/databases/monitoring/running-queries/image-20250512-110402.png) +Databases > Monitoring > Running Queries
Databases > Monitoring > Running Queries
@@ -24,7 +24,7 @@ Databases > Monitoring > Running Queries 2. Logs are displayed in descending order based on the current day. 3. Click the filter button in the top left of the table to filter with the following AND/OR conditions:
- ![image-20240730-081641.png](/administrator-manual/databases/monitoring/running-queries/image-20240730-081641.png) + image-20240730-081641.png
1. **SQL Type**: SQL statement type 2. **Action At**: Query execution date and time range @@ -61,7 +61,7 @@ Databases > Monitoring > Running Queries You can view detailed information by clicking on each row.
-![Databases > Monitoring > Running Queries > Running Query Details](/administrator-manual/databases/monitoring/running-queries/image-20250512-110509.png) +Databases > Monitoring > Running Queries > Running Query Details
Databases > Monitoring > Running Queries > Running Query Details
@@ -95,7 +95,7 @@ If you want to stop them, you must stop the session in Proxy Management.
-![Stopping Queries](/administrator-manual/databases/monitoring/running-queries/image-20250512-111342.png) +Stopping Queries
Stopping Queries
diff --git a/src/content/en/administrator-manual/databases/new-policy-management.mdx b/src/content/en/administrator-manual/databases/new-policy-management.mdx index 5c1c76a8..6dcb07dd 100644 --- a/src/content/en/administrator-manual/databases/new-policy-management.mdx +++ b/src/content/en/administrator-manual/databases/new-policy-management.mdx @@ -25,7 +25,7 @@ In General > Company Management > Security, set New DAC Policy Management (Default value: Disable)
-![Enable New DAC Policy Management](/administrator-manual/databases/new-policy-management/image-20250307-114537.png) +Enable New DAC Policy Management
Enable New DAC Policy Management
diff --git a/src/content/en/administrator-manual/databases/new-policy-management/data-paths.mdx b/src/content/en/administrator-manual/databases/new-policy-management/data-paths.mdx index 25e3d247..3081fee6 100644 --- a/src/content/en/administrator-manual/databases/new-policy-management/data-paths.mdx +++ b/src/content/en/administrator-manual/databases/new-policy-management/data-paths.mdx @@ -25,7 +25,7 @@ These configured tags are used for data classification and policy application. Table tagging can be managed in the Data Paths menu, allowing you to systematically classify and manage tables through tags.
-![image-20250307-121743.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-121743.png) +image-20250307-121743.png
1. Click **Data Paths** under the **Policy Management** section in the left sidebar. @@ -38,7 +38,7 @@ Table tagging can be managed in the Data Paths menu, allowing you to systematica 5. After entering all information, click the **OK** button to add the table.
-![image-20250307-122237.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-122237.png) +image-20250307-122237.png
1. When the table is added, it appears in the list, and you can click the **"Add Tags"** button on the detail page to add new tags. @@ -59,7 +59,7 @@ Column tagging can also be managed in the Data Paths menu. You can systematically classify columns through tags and effectively apply policies such as masking in bulk.
-![image-20250307-124339.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-124339.png) +image-20250307-124339.png
1. **Data Paths** menu's top tabs, select the **Columns** tab. @@ -72,7 +72,7 @@ You can systematically classify columns through tags and effectively apply polic 4. After entering all information, click the **OK** button to add the column.
-![image-20250307-124802.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-124802.png) +image-20250307-124802.png
1. When the column is added, it appears in the list, and you can click the **"Add Tags"** button on the detail page to add new tags. @@ -108,7 +108,7 @@ The permission granting process consists of two main steps: 2. Setting tag-based access control within granted permissions (Access Type)
-![image-20250307-125727.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-125727.png) +image-20250307-125727.png
1. **Access Control** menu, select the user to set access permissions and **Grant Permission** to grant permissions. diff --git a/src/content/en/administrator-manual/databases/new-policy-management/data-policies.mdx b/src/content/en/administrator-manual/databases/new-policy-management/data-policies.mdx index 83f1e98a..470b6f1e 100644 --- a/src/content/en/administrator-manual/databases/new-policy-management/data-policies.mdx +++ b/src/content/en/administrator-manual/databases/new-policy-management/data-policies.mdx @@ -15,7 +15,7 @@ Through this feature, you can manage data security, privacy protection, and regu ### Accessing Policy Creation Screen
-![image-20250307-131024.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131024.png) +image-20250307-131024.png
1. Expand the **Policy Management** section in the left sidebar. @@ -26,7 +26,7 @@ Through this feature, you can manage data security, privacy protection, and regu ### Setting Basic Policy Information
-![image-20250307-131052.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131052.png) +image-20250307-131052.png
In the **Information** section of the policy creation screen, set the following information: @@ -45,27 +45,27 @@ QueryPie provides the following policy types: * Uses regex-based masking patterns to detect and mask specific data patterns. (Masking Patterns) * When users query the column, it displays as `{masked}` and clicking the cell shows the masked data.

- ![Screenshot-2025-03-07-at-10.23.47-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-10.23.47-PM.png) + Screenshot-2025-03-07-at-10.23.47-PM.png
2. **Table Access Restriction** * Applies access blocking policy to tables. * When users try to query the table, access is blocked and a no permission message is displayed. * Message: `"You don't have permission to access the table 'database.table'. Please check your privileges."`

- ![Screenshot-2025-03-07-at-10.36.58-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-10.36.58-PM.png) + Screenshot-2025-03-07-at-10.36.58-PM.png
3. **Column Access Restriction** * Applies access blocking policy to columns. * When users try to query the column, it displays as `{restricted}` and access is blocked.

- ![Screenshot-2025-03-07-at-10.34.20-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-10.34.20-PM.png) + Screenshot-2025-03-07-at-10.34.20-PM.png
4. **Table Access Justification Requirement** * Enforces reason input when performing operations on specific tables. * When users perform selected operations (e.g., SELECT queries, data export), a reason input modal is displayed. * The entered reason is recorded in the Execution Reason of Query Audit.
- ![Screenshot-2025-03-07-at-11.01.28-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-11.01.28-PM.png) + Screenshot-2025-03-07-at-11.01.28-PM.png
5. **Sensitive Data Access Monitoring** * Allows administrators to designate specific tables or columns as sensitive information and generate alerts when accessed. @@ -74,14 +74,14 @@ QueryPie provides the following policy types: * Forces approval procedures through Workflow when performing `INSERT`, `UPDATE`, `DELETE` queries on specific tables. * Before creating this policy, you must first create an Approval Rule of SQL Request Type in General > Workflow Management > Approval Rules. Performing `INSERT`, `UPDATE`, `DELETE` assumes that the person performing has the corresponding privilege. To allow the person executing the query to be the requester, the "Allow Assignee selection (All Users)" option must be selected in the Execution item's Assignee for Execution as shown in the figure below, so that people with `INSERT`, `UPDATE`, `DELETE` privileges but who are not administrators can execute queries through approval.
- ![General > Workflow Management > Approval Rules creating SQL Request format Approval rule](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-153240.png) + General > Workflow Management > Approval Rules creating SQL Request format Approval rule
General > Workflow Management > Approval Rules creating SQL Request format Approval rule
* If an Approval Rule is created, you can specify the Approval Rule to link with the policy as shown in the figure below.
- ![Databases>Policy Management>Data Policies specifying pre-created SQL Request format Approval Rule](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-154218.png) + Databases>Policy Management>Data Policies specifying pre-created SQL Request format Approval Rule
Databases>Policy Management>Data Policies specifying pre-created SQL Request format Approval Rule
@@ -93,7 +93,7 @@ QueryPie provides the following policy types: In the **User Scope** section of the policy creation screen, set the user scope to which the policy will be applied.
-![image-20250307-131315.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131315.png) +image-20250307-131315.png
#### Scope Type @@ -119,7 +119,7 @@ That is, they are always applied while the policy exists. In the **Data Scope** section of the policy creation screen, set the data to which the policy will be applied.
-![image-20250307-131634.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131634.png) +image-20250307-131634.png
#### Scope Type @@ -134,13 +134,13 @@ Also, multiple tables or columns can be selected and registered as targets. 2. **Specific data path**: An option to directly specify specific data paths. **[11.0.0]** * After selecting this option, click the Add target button to specify Database, Schema, Table, Column in the popup dialog, and regular expressions can also be used.

- ![Direct path specification](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-162342.png) + Direct path specification
Direct path specification
- ![Specifying targets using regular expressions](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-162448.png) + Specifying targets using regular expressions
Specifying targets using regular expressions
diff --git a/src/content/en/administrator-manual/databases/new-policy-management/exception-management.mdx b/src/content/en/administrator-manual/databases/new-policy-management/exception-management.mdx index 8ca97637..2493f56b 100644 --- a/src/content/en/administrator-manual/databases/new-policy-management/exception-management.mdx +++ b/src/content/en/administrator-manual/databases/new-policy-management/exception-management.mdx @@ -14,7 +14,7 @@ Previous DAC policies only allowed policy exceptions through Workflow exception ### Policy Exception Management Through Workflow
-![image-20250629-172021.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250629-172021.png) +image-20250629-172021.png
The Workflow tab in Databases > Data Policies > Exception Management displays temporary policy exceptions submitted through Workflow and approved, and you can manage their active status. @@ -34,7 +34,7 @@ The Workflow tab in Databases > Data Policies > Exception Management displ ### Administrators Directly Setting Policy Exceptions
-![Manual tab of Databases > Policy Management > Exception Management](/administrator-manual/databases/new-policy-management/exception-management/image-20250727-211515.png) +Manual tab of Databases > Policy Management > Exception Management
Manual tab of Databases > Policy Management > Exception Management
@@ -53,7 +53,7 @@ In 11.3.0, it has been changed to allow specifying specific data paths using reg
-![Manual Policy Exception Creation](/administrator-manual/databases/new-policy-management/exception-management/image-20250727-210957.png) +Manual Policy Exception Creation
Manual Policy Exception Creation
@@ -85,7 +85,7 @@ When administrators create policy exceptions, the policy exception status is mai You can immediately change the status by selecting Active or Inactive in the Status column of the list, so you can easily respond without deleting or creating new policy exceptions.
-![image-20250716-055008.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250716-055008.png) +image-20250716-055008.png
#### Modifying Manually Created Policy Exceptions @@ -94,14 +94,14 @@ You can modify the settings by clicking on a specific policy exception row in th (Exception Type cannot be changed.)
-![image-20250716-055149.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250716-055149.png) +image-20250716-055149.png
#### Deleting Manually Created Policy Exceptions
-![image-20250716-055525.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250716-055525.png) +image-20250716-055525.png
diff --git a/src/content/en/administrator-manual/databases/policies/data-access.mdx b/src/content/en/administrator-manual/databases/policies/data-access.mdx index 527a48e4..41dbd168 100644 --- a/src/content/en/administrator-manual/databases/policies/data-access.mdx +++ b/src/content/en/administrator-manual/databases/policies/data-access.mdx @@ -16,7 +16,7 @@ In the Data Access menu, you can select connections to set policies, create poli Register new table/column access restriction policies by connection.
-![Administrator > Databases > Policies > Data Access ](/administrator-manual/databases/policies/data-access/image-20240725-072304.png) +Administrator > Databases > Policies > Data Access
Administrator > Databases > Policies > Data Access
@@ -35,7 +35,7 @@ You can check that the policy has been created in the Data Access policy list. ### Registering Rules in Table/Column Access Restriction Policies
-![Administrator > Databases > Policies > Data Access > Details > Add Rule](/administrator-manual/databases/policies/data-access/data-access-02.png) +Administrator > Databases > Policies > Data Access > Details > Add Rule
Administrator > Databases > Policies > Data Access > Details > Add Rule
@@ -57,7 +57,7 @@ You can check that rules are registered in the Rule List tab. Now when users query the data, if policy is applied to the table, the table itself cannot be queried, and if rules are applied to columns, it is displayed as *`{RESTRICTED}`* .
-![SQL Editor > Displayed as *`{RESTRICTED}`* when querying data with applied policies](/administrator-manual/databases/policies/data-access/data-access-03.png) +SQL Editor > Displayed as *`{RESTRICTED}`* when querying data with applied policies
SQL Editor > Displayed as *`{RESTRICTED}`* when querying data with applied policies
@@ -77,7 +77,7 @@ From version 10.3.0, you can check access logs for tables and columns restricted
-![Checking logs in Logs tab](/administrator-manual/databases/policies/data-access/image-20250512-040339.png) +Checking logs in Logs tab
Checking logs in Logs tab
@@ -95,7 +95,7 @@ Checking logs in Logs tab 7. **Action At** : Time when the query was performed. 4. Click on rows in the Log tab to check the executed query in the detail screen.
- ![Checking query content in detailed log view](/administrator-manual/databases/policies/data-access/image-20250512-040436.png) + Checking query content in detailed log view
Checking query content in detailed log view
diff --git a/src/content/en/administrator-manual/databases/policies/data-masking.mdx b/src/content/en/administrator-manual/databases/policies/data-masking.mdx index 033c23d1..cc8d7949 100644 --- a/src/content/en/administrator-manual/databases/policies/data-masking.mdx +++ b/src/content/en/administrator-manual/databases/policies/data-masking.mdx @@ -17,7 +17,7 @@ In the Data Masking menu, you can select the connection for which to set policie Register new masking policies by connection.
-![Administrator > Databases > Policies > Data Masking](/administrator-manual/databases/policies/data-masking/image-20240725-072925.png) +Administrator > Databases > Policies > Data Masking
Administrator > Databases > Policies > Data Masking
@@ -36,7 +36,7 @@ You can confirm that the policy has been created in the Data Masking policy list ### Registering Rules in Data Masking Policies
-![Administrator > Databases > Policies > Data Masking > Rule Details](/administrator-manual/databases/policies/data-masking/image-20240725-073032.png) +Administrator > Databases > Policies > Data Masking > Rule Details
Administrator > Databases > Policies > Data Masking > Rule Details
@@ -76,7 +76,7 @@ From version 10.3.0, you can check access logs for columns controlled by masking
-![image-20250512-041023.png](/administrator-manual/databases/policies/data-masking/image-20250512-041023.png) +image-20250512-041023.png
1. Click on the individual item (row) of the policy you created in the policy list to navigate to the details page. diff --git a/src/content/en/administrator-manual/databases/policies/masking-pattern.mdx b/src/content/en/administrator-manual/databases/policies/masking-pattern.mdx index d9826e44..08dd9e62 100644 --- a/src/content/en/administrator-manual/databases/policies/masking-pattern.mdx +++ b/src/content/en/administrator-manual/databases/policies/masking-pattern.mdx @@ -22,7 +22,7 @@ You can view registered masking patterns on the Masking Pattern page. (Searchable by pattern name)
-![Administrator > Databases > General > Masking Pattern](/administrator-manual/databases/policies/masking-pattern/image-20250826-005621.png) +Administrator > Databases > General > Masking Pattern
Administrator > Databases > General > Masking Pattern
@@ -34,7 +34,7 @@ Administrator > Databases > General > Masking Pattern Clicking on an item in the table you want to view details for opens a Drawer where you can view, modify, or delete detailed information.
-![Administrator > Databases > General > Masking Pattern > Details](/administrator-manual/databases/policies/masking-pattern/image-20250826-005930.png) +Administrator > Databases > General > Masking Pattern > Details
Administrator > Databases > General > Masking Pattern > Details
@@ -60,7 +60,7 @@ Alternatively, you can select items to delete using checkboxes in the Masking Pa After entering all necessary information, click the `Save` button to save.
-![Create Pattern](/administrator-manual/databases/policies/masking-pattern/screenshot-20240731-174002.png) +Create Pattern
Create Pattern
diff --git a/src/content/en/administrator-manual/databases/policies/policy-exception.mdx b/src/content/en/administrator-manual/databases/policies/policy-exception.mdx index d3578c6a..475cec4f 100644 --- a/src/content/en/administrator-manual/databases/policies/policy-exception.mdx +++ b/src/content/en/administrator-manual/databases/policies/policy-exception.mdx @@ -10,7 +10,7 @@ When an Unmasking Request submitted through Workflow is approved, the content is
-![Policy Exception](/administrator-manual/databases/policies/policy-exception/image-20241101-011820.png) +Policy Exception
Policy Exception
diff --git a/src/content/en/administrator-manual/databases/policies/sensitive-data.mdx b/src/content/en/administrator-manual/databases/policies/sensitive-data.mdx index 2f44bb23..3a655dd9 100644 --- a/src/content/en/administrator-manual/databases/policies/sensitive-data.mdx +++ b/src/content/en/administrator-manual/databases/policies/sensitive-data.mdx @@ -18,7 +18,7 @@ When created as a policy, you can check access records to sensitive data through Register new sensitive data policies by connection.
-![Administrator > Databases > Policies > Sensitive Data](/administrator-manual/databases/policies/sensitive-data/image-20240729-054311.png) +Administrator > Databases > Policies > Sensitive Data
Administrator > Databases > Policies > Sensitive Data
@@ -39,7 +39,7 @@ You can confirm that the policy has been created in the Sensitive Data policy li After creating a policy, register the path of the data to which the policy will be applied as a rule.
-![Administrator > Databases > Policies > Sensitive Data > Rule List](/administrator-manual/databases/policies/sensitive-data/image-20240820-120656.png) +Administrator > Databases > Policies > Sensitive Data > Rule List
Administrator > Databases > Policies > Sensitive Data > Rule List
@@ -64,7 +64,7 @@ To set up sensitive data policies as notifications, refer to the [Alerts](../../ From version 10.2.8, the sensitive data access history visible in the Log tab has been improved to include queries performed by users. Click on a Log row to see the detailed information including the query performed by the user.
-![Sensitive Data Log Query Content Display](/administrator-manual/databases/policies/sensitive-data/image-20250410-065516.png) +Sensitive Data Log Query Content Display
Sensitive Data Log Query Content Display
diff --git a/src/content/en/administrator-manual/general.mdx b/src/content/en/administrator-manual/general.mdx index 17196b96..fa3c70be 100644 --- a/src/content/en/administrator-manual/general.mdx +++ b/src/content/en/administrator-manual/general.mdx @@ -9,7 +9,7 @@ title: 'General' General is the first gateway to the administrator page and a page for managing various general settings across QueryPie, including security settings management, user and group management, workflow approval line management, integration connections, and API token management.
-![Administrator > General > Company Management > Security](/administrator-manual/general/image-20240724-054109.png) +Administrator > General > Company Management > Security
Administrator > General > Company Management > Security
diff --git a/src/content/en/administrator-manual/general/company-management.mdx b/src/content/en/administrator-manual/general/company-management.mdx index 9d0c5b54..6760ab7b 100644 --- a/src/content/en/administrator-manual/general/company-management.mdx +++ b/src/content/en/administrator-manual/general/company-management.mdx @@ -9,7 +9,7 @@ title: 'Company Management' Company Management is a menu for managing basic security and notification settings for the QueryPie product.
-![Administrator > General > Company Management > General](/administrator-manual/general/company-management/image-20240724-055809.png) +Administrator > General > Company Management > General
Administrator > General > Company Management > General
diff --git a/src/content/en/administrator-manual/general/company-management/alerts.mdx b/src/content/en/administrator-manual/general/company-management/alerts.mdx index bebddb3b..b4f281e9 100644 --- a/src/content/en/administrator-manual/general/company-management/alerts.mdx +++ b/src/content/en/administrator-manual/general/company-management/alerts.mdx @@ -13,7 +13,7 @@ By pre-setting trigger conditions for major anomalies, you can detect policy vio This allows for rapid identification and resolution of potential security incidents, and protection of sensitive information such as queries or data leaks that exceed predefined thresholds.
-![Administrator > General > Company Management > Alerts](/administrator-manual/general/company-management/alerts/screenshot-20240728-223320.png) +Administrator > General > Company Management > Alerts
Administrator > General > Company Management > Alerts
@@ -196,7 +196,7 @@ From version 11.1.0, when the New DAC Policy Management feature is activated, yo `Create Alert` Click the button in the top right corner of the Alerts page to create a new alert. `OK` Click the button to complete alert creation.
-![Administrator > General > Company Management > Alerts > Create Alert](/administrator-manual/general/company-management/alerts/screenshot-20240729-141728.png) +Administrator > General > Company Management > Alerts > Create Alert
Administrator > General > Company Management > Alerts > Create Alert
@@ -396,7 +396,7 @@ Example) With the following settings, an alert is sent when 3 server connection * Specific Time Internal (Minutes) : 5
-![image-20251010-093016.png](/administrator-manual/general/company-management/alerts/image-20251010-093016.png) +image-20251010-093016.png
@@ -470,7 +470,7 @@ This can only be used when the New DAC Policy Management feature is enabled in D Data Access alerts can select four **policy types**: Column Data Masking, Table Access Restriction, Column Access Restriction, and Sensitive Data Access Monitoring.
-![image-20250727-222007.png](/administrator-manual/general/company-management/alerts/image-20250727-222007.png) +image-20250727-222007.png
* **Column Data Masking** @@ -504,7 +504,7 @@ In the Details tab of the detail page, you can view and modify the alert conditi `Save Changes` Click the button in the top right corner to apply the modifications.
-![Administrator > General > Company Management > Alerts > List Details (Details)](/administrator-manual/general/company-management/alerts/screenshot-20240729-154217.png) +Administrator > General > Company Management > Alerts > List Details (Details)
Administrator > General > Company Management > Alerts > List Details (Details)
@@ -517,7 +517,7 @@ Select the alert you want to view delivery history for in the Alerts list. You can then view the history in the Log section of the detail page.
-![Administrator > General > Company Management > Alerts > List Details (Logs)](/administrator-manual/general/company-management/alerts/screenshot-20240729-154223.png) +Administrator > General > Company Management > Alerts > List Details (Logs)
Administrator > General > Company Management > Alerts > List Details (Logs)
diff --git a/src/content/en/administrator-manual/general/company-management/allowed-zones.mdx b/src/content/en/administrator-manual/general/company-management/allowed-zones.mdx index c72e5089..6880e2f2 100644 --- a/src/content/en/administrator-manual/general/company-management/allowed-zones.mdx +++ b/src/content/en/administrator-manual/general/company-management/allowed-zones.mdx @@ -25,7 +25,7 @@ You can search by Allowed Zone name.
-![Administrator > General > Company Management > Allowed Zones](/administrator-manual/general/company-management/allowed-zones/image-20251009-030815.png) +Administrator > General > Company Management > Allowed Zones
Administrator > General > Company Management > Allowed Zones
@@ -36,7 +36,7 @@ Administrator > General > Company Management > Allowed Zones Click on the item you want to view details for in the Allowed Zones list to open a drawer.
-![Administrator > General > Company Management > Allowed Zones > Allowed Zones Detail](/administrator-manual/general/company-management/allowed-zones/image-20251009-031233.png) +Administrator > General > Company Management > Allowed Zones > Allowed Zones Detail
Administrator > General > Company Management > Allowed Zones > Allowed Zones Detail
@@ -61,7 +61,7 @@ In the Mapped List by Allowed Zones area within the drawer, you can check DB con Click the `Create Allowed Zone` button on the Allowed Zone list page to display the Allowed Zone input fields.
-![Input fields displayed when creating Allowed Zone](/administrator-manual/general/company-management/allowed-zones/image-20251009-031536.png) +Input fields displayed when creating Allowed Zone
Input fields displayed when creating Allowed Zone
@@ -82,7 +82,7 @@ Select the Allowed Zone you want to delete with a checkbox in the Allowed Zone l Click the button and then click the `Delete` button in the confirmation modal to complete the deletion.
-![Delete Option Activated](/administrator-manual/general/company-management/allowed-zones/screenshot-20240730-220112.png) +Delete Option Activated
Delete Option Activated
diff --git a/src/content/en/administrator-manual/general/company-management/channels.mdx b/src/content/en/administrator-manual/general/company-management/channels.mdx index 683a552f..dc83619b 100644 --- a/src/content/en/administrator-manual/general/company-management/channels.mdx +++ b/src/content/en/administrator-manual/general/company-management/channels.mdx @@ -17,7 +17,7 @@ You can view the list of currently registered channels in the Administrator > You can search by channel name and filter by Channel Type.
-![Administrator > General > Company Management > Channels](/administrator-manual/general/company-management/channels/screenshot-20240808-172741.png) +Administrator > General > Company Management > Channels
Administrator > General > Company Management > Channels
@@ -26,7 +26,7 @@ Administrator > General > Company Management > Channels Clicking on items in the list allows you to view and modify detailed information.
-![Administrator > General > Company Management > Channels > List Details](/administrator-manual/general/company-management/channels/screenshot-20241211-191603.png) +Administrator > General > Company Management > Channels > List Details
Administrator > General > Company Management > Channels > List Details
@@ -38,7 +38,7 @@ Administrator > General > Company Management > Channels > List Detai `Create Channel` Click the button in the top right corner of the Channels page to display the channel creation modal.
-![Administrator > General > Company Management > Channels > Create Channel](/administrator-manual/general/company-management/channels/screenshot-20241211-154231.png) +Administrator > General > Company Management > Channels > Create Channel
Administrator > General > Company Management > Channels > Create Channel
@@ -109,7 +109,7 @@ Select the channel you want to delete with a checkbox in the channel list within Click the button to display a deletion confirmation modal. `OK` Click the button to complete the deletion.
-![Administrator > General > Company Management > Channels > Delete confirmation modal](/administrator-manual/general/company-management/channels/screenshot-20240728-222004.png) +Administrator > General > Company Management > Channels > Delete confirmation modal
Administrator > General > Company Management > Channels > Delete confirmation modal
@@ -120,7 +120,7 @@ Administrator > General > Company Management > Channels > Delete con #### 1. Creating an App
-![Slack API > Apps > Create an App](/administrator-manual/general/company-management/channels/screenshot-20240305-161015.png) +Slack API > Apps > Create an App
Slack API > Apps > Create an App
@@ -134,7 +134,7 @@ Slack API > Apps > Create an App #### 2-1. Integrating with Webhook Type
-![Slack API > Apps > Settings > Incoming Webhooks](/administrator-manual/general/company-management/channels/screenshot-20240804-190716.png) +Slack API > Apps > Settings > Incoming Webhooks
Slack API > Apps > Settings > Incoming Webhooks
@@ -145,7 +145,7 @@ Slack API > Apps > Settings > Incoming Webhooks 3. Click `Add New Webhook to Workspace` at the bottom.
-![Webhook addition screen in Slack](/administrator-manual/general/company-management/channels/image-20240305-110658.png) +Webhook addition screen in Slack
Webhook addition screen in Slack
@@ -159,7 +159,7 @@ Webhook addition screen in Slack 1. Click the created App to enter the app's Settings page, then navigate to the `App Manifest` menu. 2. Add `chat:write`, `users:read`, `users:read.email` to the scopes area and save.
- ![Slack API > Apps > Settings > App Manifest](/administrator-manual/general/company-management/channels/screenshot-20241211-171140.png) + Slack API > Apps > Settings > App Manifest
Slack API > Apps > Settings > App Manifest
@@ -170,14 +170,14 @@ Webhook addition screen in Slack 5. Go to the corresponding Slack channel and add the created app. (If the app is already added, you can skip this step) 6. Click the channel name to open the Channel Detail modal, and copy the Channel ID from the bottom of the modal. Paste the copied Channel ID into the QueryPie channel creation modal.
- ![Slack App > Channel Detail](/administrator-manual/general/company-management/channels/screenshot-20241211-190312.png) + Slack App > Channel Detail
Slack App > Channel Detail
7. Copy the Bot User OAuth Token from the OAuth & Permissions page and paste it into the QueryPie channel creation modal.
- ![Slack OAuth & Permissions page - Copy token](/administrator-manual/general/company-management/channels/screenshot-20240804-190835.png) + Slack OAuth & Permissions page - Copy token
Slack OAuth & Permissions page - Copy token
diff --git a/src/content/en/administrator-manual/general/company-management/general.mdx b/src/content/en/administrator-manual/general/company-management/general.mdx index 405d20bd..d88e3d53 100644 --- a/src/content/en/administrator-manual/general/company-management/general.mdx +++ b/src/content/en/administrator-manual/general/company-management/general.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' The General page allows you to change basic settings for the entire QueryPie.
-![Administrator > General > Company Management > General](/administrator-manual/general/company-management/general/image-20250822-103044.png) +Administrator > General > Company Management > General
Administrator > General > Company Management > General
@@ -33,7 +33,7 @@ Administrator > General > Company Management > General The System Properties page allows you to view configuration values of QueryPie system components and save them as files.
-![Administrator > General > Company Management > General > System Properties](/administrator-manual/general/company-management/general/image-20240805-014838.png) +Administrator > General > Company Management > General > System Properties
Administrator > General > Company Management > General > System Properties
@@ -45,7 +45,7 @@ Administrator > General > Company Management > General > System Prop Workflow Configurations allows you to change settings related to approval submission and approval.
-![Screenshot-2025-08-25-at-5.36.19-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-08-25-at-5.36.19-PM.png) +Screenshot-2025-08-25-at-5.36.19-PM.png
### Maximum Approval Period Setting @@ -101,27 +101,27 @@ You can automatically assign approvers based on specific Attributes (e.g., team * Important: * The value of the selected Attribute must contain the QueryPie Login ID of the approver.
- ![Admin > General > Users > Detail page > Profile tab
](/administrator-manual/general/company-management/general/Screenshot-2025-06-12-at-1.33.58-PM.png) + Admin > General > Users > Detail page > Profile tab<br/>
Admin > General > Users > Detail page > Profile tab
* In the Administrator > General > Workflow Management > Approval Rules page, when adding new approval rules or modifying existing rules, select 'Allow Assignee selection (Attribute-Based)' in the 'Assignee for Approval' item, then specify the Attribute (e.g., teamLeader) to map with the approver.
- ![image-20251110-030113.png](/administrator-manual/general/company-management/general/image-20251110-030113.png) + image-20251110-030113.png
* Integration when self-approval is disabled: If the 'Self Approval (self-approval)' option is disabled in Approval Rules settings, when the approver determined based on Attributes is the requester themselves, that requester cannot be automatically assigned as an approver. In this case, approver assignment may fail or be processed through other routes according to workflow settings or system policies, so caution is needed. * Notification when Attribute value is missing * If the corresponding Attribute value is empty in the submitter's User Profile (i.e., no approver Login ID is specified), a notification modal with the following content is displayed when submitting workflows and request submission is interrupted. Submitters must contact administrators to set the Attribute value in their profile. * Error message example:
- ![image-20250508-022114.png](/administrator-manual/general/company-management/general/image-20250508-022114.png) + image-20250508-022114.png
* When Attribute value exists but the corresponding user is deactivated * If the approver specified by the corresponding Attribute value in the submitter's User Profile is deactivated, the specified approver is not displayed in the Approver field when submitting workflows, and a notification modal with the following content is displayed and request submission is interrupted. * Error message example:
- ![Screenshot-2025-06-16-at-10.30.14-AM.png](/administrator-manual/general/company-management/general/Screenshot-2025-06-16-at-10.30.14-AM.png) + Screenshot-2025-06-16-at-10.30.14-AM.png
### Attribute-Based Workflow Menu Hiding Feature (Use User Attribute to Hide Workflow Menu) @@ -129,7 +129,7 @@ You can automatically assign approvers based on specific Attributes (e.g., team Activate the Use User Attribute to Hide Workflow Menu toggle.
-![Screenshot-2025-06-26-at-6.35.32-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-06-26-at-6.35.32-PM.png) +Screenshot-2025-06-26-at-6.35.32-PM.png
This is a feature to hide the Workflow menu from the user dashboard based on specific user attributes (User Attribute). @@ -149,14 +149,14 @@ This option allows administrators to enable or disable delegated approval, a fea If disabled, the Approver setting menu will not be displayed on the user preferences screen.
-![Allow Delegated Approval switch](/administrator-manual/general/company-management/general/image-20250926-112444.png) +Allow Delegated Approval switch
Allow Delegated Approval switch
-![Preferences with delegated approval disabled](/administrator-manual/general/company-management/general/image-20250926-112201.png) +Preferences with delegated approval disabled
Preferences with delegated approval disabled
@@ -167,7 +167,7 @@ Preferences with delegated approval disabled When the toggle is turned on, throttling is applied when executing SQL requests submitted in Workflow.
-![Screenshot-2025-05-09-at-3.18.32-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-05-09-at-3.18.32-PM.png) +Screenshot-2025-05-09-at-3.18.32-PM.png
@@ -183,7 +183,7 @@ This prevents DB load from large-scale query execution. Activate the Redirect to custom page for SQL Requests toggle.
-![Screenshot-2025-05-09-at-8.33.07-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-05-09-at-8.33.07-PM.png) +Screenshot-2025-05-09-at-8.33.07-PM.png
This option determines whether to redirect users to a pre-defined custom URL page when `Send Request` clicking the button when workflow approval requests occur due to INSERT, UPDATE, DELETE query execution on Ledger tables in User Agent. @@ -201,7 +201,7 @@ This allows customers to strengthen integration with their own external workflow Activate the Select Request Types Allowed for Users toggle.
-![Screenshot-2025-05-09-at-8.40.28-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-05-09-at-8.40.28-PM.png) +Screenshot-2025-05-09-at-8.40.28-PM.png
This option allows administrators to selectively control the request types of workflows that users can access and request. @@ -227,7 +227,7 @@ This option allows administrators to selectively control the request types of wo To specify approval lines (Approval Rule) according to requested permissions when submitting DB Access Request through Workflow, activate the "Use DB Privilege Type Based Approval" toggle.
-![Use DB Privilege Type Based Approval](/administrator-manual/general/company-management/general/image-20250822-111454.png) +Use DB Privilege Type Based Approval
Use DB Privilege Type Based Approval
@@ -236,7 +236,7 @@ Use DB Privilege Type Based Approval `+Routing Rule` Click the button to specify conditions for privileges and set routing for approval lines.
-![image-20250822-112026.png](/administrator-manual/general/company-management/general/image-20250822-112026.png) +image-20250822-112026.png
* **Routing Rule Name** : Enter an easily identifiable name for the routing rule. @@ -262,7 +262,7 @@ Use DB Privilege Type Based Approval Provides options to activate or deactivate the "Attach Explain Results" feature that attaches execution plan results when submitting queries to be performed through Workflow's SQL Request.
-![image-20250825-002423.png](/administrator-manual/general/company-management/general/image-20250825-002423.png) +image-20250825-002423.png
Even if administrators activate this option, "Attach Explain Results" in the Workflow's SQL Request form is set to Off, so users must explicitly change the "Attach Explain Results" toggle switch to On when needed for execution plan results to be attached. \ No newline at end of file diff --git a/src/content/en/administrator-manual/general/company-management/licenses.mdx b/src/content/en/administrator-manual/general/company-management/licenses.mdx index ef2d9dde..3abb7a4e 100644 --- a/src/content/en/administrator-manual/general/company-management/licenses.mdx +++ b/src/content/en/administrator-manual/general/company-management/licenses.mdx @@ -19,7 +19,7 @@ Invalid licenses are displayed in the Expired License list and cannot be selecte
-![Administrator > General > Company Management > Licenses](/administrator-manual/general/company-management/licenses/image-20250926-124941.png) +Administrator > General > Company Management > Licenses
Administrator > General > Company Management > Licenses
diff --git a/src/content/en/administrator-manual/general/company-management/security.mdx b/src/content/en/administrator-manual/general/company-management/security.mdx index 42d26809..a8f80c3f 100644 --- a/src/content/en/administrator-manual/general/company-management/security.mdx +++ b/src/content/en/administrator-manual/general/company-management/security.mdx @@ -25,7 +25,7 @@ Manage security settings related to QueryPie Web login. You can set security policies such as account lockout and expiration for QueryPie accounts.
-![Screenshot-2025-08-27-at-4.25.50-PM.png](/administrator-manual/general/company-management/security/Screenshot-2025-08-27-at-4.25.50-PM.png) +Screenshot-2025-08-27-at-4.25.50-PM.png
* **Account Expiration Period (Days)** : Criteria for long-term inactivity to process account expiration @@ -48,7 +48,7 @@ You can set security policies such as account lockout and expiration for QueryPi You can set password policies for QueryPie accounts.
-![image-20250515-091250.png](/administrator-manual/general/company-management/security/image-20250515-091250.png) +image-20250515-091250.png
* **Maximum Password Age** : Password change cycle (Default: 90 days) @@ -71,7 +71,7 @@ You can set password policies for QueryPie accounts. You can set timeout policies for web console and agents.
-![image-20251009-051727.png](/administrator-manual/general/company-management/security/image-20251009-051727.png) +image-20251009-051727.png
* **Web Inactivity Timeout** : Web console timeout criteria (Default: 60 minutes) @@ -95,7 +95,7 @@ You can set timeout policies for web console and agents. You can set IP restriction policies when accessing QueryPie.
-![Screenshot-2025-06-26-at-2.14.46-PM.png](/administrator-manual/general/company-management/security/Screenshot-2025-06-26-at-2.14.46-PM.png) +Screenshot-2025-06-26-at-2.14.46-PM.png
* **All Users** : IP restriction settings applied to all users (Default: 0.0.0.0/0) @@ -115,7 +115,7 @@ Users blocked from login due to enabling the `Require Allowed Zones for User Acc * **Admin Page Access Control** : Sets policies to restrict IPs of administrators who can access the administrator page. You can restrict access to the administrator page only to administrators connecting from specific IP addresses or ranges by enabling the toggle.
- ![Screen when Admin page IP access is blocked](/administrator-manual/general/company-management/security/image-20251212-161723.png) + Screen when Admin page IP access is blocked
Screen when Admin page IP access is blocked
@@ -134,14 +134,14 @@ If the default value (0.0.0.0/0) is registered in All Users and specific Allowed
-![Screen when IP access is blocked by Each User settings](/administrator-manual/general/company-management/security/image-20251218-082726.png) +Screen when IP access is blocked by Each User settings
Screen when IP access is blocked by Each User settings
-![Screen when IP access is blocked by All User settings](/administrator-manual/general/company-management/security/image-20251212-162103.png) +Screen when IP access is blocked by All User settings
Screen when IP access is blocked by All User settings
@@ -161,7 +161,7 @@ Sets whether to use Secret Store. Currently supports HashiCorp Vault.
-![screenshot-20240726-152042.png](/administrator-manual/general/company-management/security/screenshot-20240726-152042.png) +screenshot-20240726-152042.png
Vault registration is performed in the General > Integrations menu. @@ -176,14 +176,14 @@ The toggle can be disabled after all registered Vaults are removed. After Secret Store usage activation and Vault registration are completed, you can select the authentication information storage in the DB connection detail page or Server Group detail page.
-![DB Connection detail page > Connection Information > Secret Store selection](/administrator-manual/general/company-management/security/screenshot-20240726-185946.png) +DB Connection detail page > Connection Information > Secret Store selection
DB Connection detail page > Connection Information > Secret Store selection
-![Server Group detail page > Accounts > Secret Store selection](/administrator-manual/general/company-management/security/screenshot-20240726-190034.png) +Server Group detail page > Accounts > Secret Store selection
Server Group detail page > Accounts > Secret Store selection
@@ -198,7 +198,7 @@ In 11.3.0, client configuration was improved to support multiple configurations Manages other security settings.
-![screenshot-20240726-152051.png](/administrator-manual/general/company-management/security/screenshot-20240726-152051.png) +screenshot-20240726-152051.png
* Export a file with Encryption : Whether to enter password when downloading files diff --git a/src/content/en/administrator-manual/general/system/api-token.mdx b/src/content/en/administrator-manual/general/system/api-token.mdx index 0c30ec7d..12bb87ab 100644 --- a/src/content/en/administrator-manual/general/system/api-token.mdx +++ b/src/content/en/administrator-manual/general/system/api-token.mdx @@ -40,7 +40,7 @@ The list of provided APIs and specifications can be found in the API documentati ### Viewing API Token List
-![Administrator > General > System > API Token](/administrator-manual/general/system/api-token/screenshot-20240723-110619.png) +Administrator > General > System > API Token
Administrator > General > System > API Token
@@ -56,7 +56,7 @@ Administrator > General > System > API Token ### Creating API Tokens
-![Administrator > General > System > API Token > Create API Token](/administrator-manual/general/system/api-token/image-20241028-094955.png) +Administrator > General > System > API Token > Create API Token
Administrator > General > System > API Token > Create API Token
@@ -77,7 +77,7 @@ Administrator > General > System > API Token > Create API Token 3. `Ok` Click the button to complete API Token creation. 4. You can view API Token information only once in the creation completion modal.
- ![General Settings > System > API Token > Create API Token](/administrator-manual/general/system/api-token/screenshot-20240723-120533.png) + General Settings > System > API Token > Create API Token
General Settings > System > API Token > Create API Token
@@ -89,7 +89,7 @@ Administrator > General > System > API Token > Create API Token ### Modifying API Tokens
-![General Settings > System > API Token > Edit API Token](/administrator-manual/general/system/api-token/image-20241028-095455.png) +General Settings > System > API Token > Edit API Token
General Settings > System > API Token > Edit API Token
@@ -121,7 +121,7 @@ General Settings > System > API Token > Edit API Token ### Deleting API Tokens
-![Administrator > General > System > API Token > Delete](/administrator-manual/general/system/api-token/screenshot-20240723-121212.png) +Administrator > General > System > API Token > Delete
Administrator > General > System > API Token > Delete
diff --git a/src/content/en/administrator-manual/general/system/integrations.mdx b/src/content/en/administrator-manual/general/system/integrations.mdx index 9b346529..f0e730e7 100644 --- a/src/content/en/administrator-manual/general/system/integrations.mdx +++ b/src/content/en/administrator-manual/general/system/integrations.mdx @@ -18,7 +18,7 @@ It can analyze log correlations, identify abnormal activities, and take appropri
-![Administrator > General > System > Integrations](/administrator-manual/general/system/integrations/image-20240714-054645.png) +Administrator > General > System > Integrations
Administrator > General > System > Integrations
diff --git a/src/content/en/administrator-manual/general/system/integrations/identity-providers.mdx b/src/content/en/administrator-manual/general/system/integrations/identity-providers.mdx index 6c9505be..c475664b 100644 --- a/src/content/en/administrator-manual/general/system/integrations/identity-providers.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/identity-providers.mdx @@ -33,7 +33,7 @@ By default, user authentication is handled using IDs and passwords stored in Que This item cannot be deleted.
-![image-20251014-010700.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-010700.png) +image-20251014-010700.png
#### Default authentication details @@ -43,7 +43,7 @@ This item cannot be deleted. * **Multi-Factor Authentication Setting** : You can configure MFA. Google Authenticator and Email are supported.
-![Internal database details](/administrator-manual/general/system/integrations/identity-providers/image-20251014-011706.png) +Internal database details
Internal database details
@@ -65,7 +65,7 @@ Click the `+ Add` button at the top right of the list, and select LDAP for Type * **Bind Password** : Enter the password for the BindDN.
-![LDAP details](/administrator-manual/general/system/integrations/identity-providers/image-20251014-012049.png) +LDAP details
LDAP details
@@ -84,7 +84,7 @@ Enter the mapping information to synchronize and map QueryPie user accounts with To synchronize user group information and membership information from LDAP, enable (check) the **Use Group option** and enter the required information.
-![image-20251014-075227.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-075227.png) +image-20251014-075227.png
@@ -167,7 +167,7 @@ If group entries contain user information, select `Include user information in g To run user information synchronization from the LDAP server, enable the **Use Synchronization with the Authentication System** option.
-![image-20251014-075127.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-075127.png) +image-20251014-075127.png
@@ -206,7 +206,7 @@ Click the `Add Row` button at the top right to add a new mapping row, and you ca When integrating Active Directory with LDAP, you must set the Anonymous option to false. AD does not allow search operations in an anonymous bind state by default.
-![image-20251222-023912.png](/administrator-manual/general/system/integrations/identity-providers/image-20251222-023912.png) +image-20251222-023912.png
@@ -215,7 +215,7 @@ AD does not allow search operations in an anonymous bind state by default. #### Add QueryPie as an application in Okta
-![Okta Admin > Applications > Applications > Browse App Catalog > Search for QueryPie](/administrator-manual/general/system/integrations/identity-providers/image-20240723-064242.png) +Okta Admin > Applications > Applications > Browse App Catalog > Search for QueryPie
Okta Admin > Applications > Applications > Browse App Catalog > Search for QueryPie
@@ -231,7 +231,7 @@ Okta Admin > Applications > Applications > Browse App Catalog > Sear #### Profile settings for Okta account integration
-![Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute](/administrator-manual/general/system/integrations/identity-providers/image-20240723-064424.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
@@ -247,7 +247,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Add Attrib * Display name: loginId / Variable name: loginId, then click `Save`
-![Okta Admin > Directory > Profile Editor > QueryPie User > Mappings](/administrator-manual/general/system/integrations/identity-providers/image-20240723-064721.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
@@ -265,7 +265,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Mappings #### Assign users to the QueryPie application added in Okta
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/system/integrations/identity-providers/image-20240723-065134.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -283,7 +283,7 @@ Okta Admin > Applications > Applications > QueryPie App #### Configure QueryPie application integration settings in Okta
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/system/integrations/identity-providers/image-20240723-065346.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -306,7 +306,7 @@ Typically, you can issue an API token using your Okta Super Administrator/Read-O However, to improve security, we recommend creating an API token with minimum permissions according to the following permissions and methods.
-![Okta Admin Console > Security > Administrators > Roles > Create new role](/administrator-manual/general/system/integrations/identity-providers/image-20240110-042233.png) +Okta Admin Console > Security > Administrators > Roles > Create new role
Okta Admin Console > Security > Administrators > Roles > Create new role
@@ -346,7 +346,7 @@ Okta Admin Console > Security > Administrators > Roles > Create new Click the `+ Add` button at the top right of the list, and select Okta for Type in the popup screen to add Okta as an IdP.
-![Okta details (1)](/administrator-manual/general/system/integrations/identity-providers/image-20251014-014729.png) +Okta details (1)
Okta details (1)
@@ -395,14 +395,14 @@ For example, when you want to set different post-login redirect pages for regula When assertions must be received at a dynamically generated ACS URL depending on specific situations or client requirements, you can guide the selection of one of the statically defined URLs through the index.
-![Audience URI (SP Entity ID) in Okta app settings](/administrator-manual/general/system/integrations/identity-providers/screenshot-20250124-164255.png) +Audience URI (SP Entity ID) in Okta app settings
Audience URI (SP Entity ID) in Okta app settings
-![Index for Other Requestable SSO URLs](/administrator-manual/general/system/integrations/identity-providers/screenshot-20250124-164553.png) +Index for Other Requestable SSO URLs
Index for Other Requestable SSO URLs
@@ -410,7 +410,7 @@ Index for Other Requestable SSO URLs
-![Okta details (2)](/administrator-manual/general/system/integrations/identity-providers/image-20251014-014805.png) +Okta details (2)
Okta details (2)
@@ -440,7 +440,7 @@ When using two or more QueryPie Applications, go to Okta Admin > Applications
-![Top URL of Okta Admin > Applications > QueryPie App](/administrator-manual/general/system/integrations/identity-providers/Authentication-Okta-02.png) +Top URL of Okta Admin > Applications > QueryPie App
Top URL of Okta Admin > Applications > QueryPie App
@@ -453,7 +453,7 @@ Top URL of Okta Admin > Applications > QueryPie App 2. You can now sign in to QueryPie with an Okta account using the `Login with Okta` button on the login page.
-![image-20251014-082704.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-082704.png) +image-20251014-082704.png
@@ -485,7 +485,7 @@ For detailed information on One Login SAML Custom Connector configuration, pleas * **Identity Provider Metadata** : Copy and paste the contents of the XML file downloaded from One Login.
-![One Login details (1)](/administrator-manual/general/system/integrations/identity-providers/image-20251020-001435.png) +One Login details (1)
One Login details (1)
@@ -495,7 +495,7 @@ One Login details (1) * To use periodic synchronization, configure Scheduling in the Replication Frequency field.
-![One Login details (2)](/administrator-manual/general/system/integrations/identity-providers/image-20251014-014949.png) +One Login details (2)
One Login details (2)
@@ -520,7 +520,7 @@ For a one-time SAML integration without periodic synchronization, configure by e * **Identity Provider Metadata** : Copy and paste the contents of the SML metadata XML confirmed in the IdP.
-![image-20251014-015015.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-015015.png) +image-20251014-015015.png
< Reference > [AWS SSO Integration](identity-providers/aws-sso-saml-20) @@ -535,7 +535,7 @@ Custom Identity Provider is used only for special cases that use an authenticati * To run user information synchronization, enable the Use Synchronization with the Authentication System option.
-![image-20251014-015047.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-015047.png) +image-20251014-015047.png
* **Additional Settings** diff --git a/src/content/en/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx b/src/content/en/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx index 6354de1f..240000f2 100644 --- a/src/content/en/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx @@ -18,7 +18,7 @@ If you configure SAML under Identity Providers Integration with Type = SAML, per ### Add QueryPie as an application in AWS IAM Identity Center
-![AWS-SSO-01-20230317-044219.png](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/AWS-SSO-01-20230317-044219.png) +AWS-SSO-01-20230317-044219.png
1. Go to [AWS IAM Identity Center](https://ap-northeast-2.console.aws.amazon.com/singlesignon/applications/home). @@ -37,7 +37,7 @@ If you configure SAML under Identity Providers Integration with Type = SAML, per ### Attribute mappings for QueryPie integration
-![AWS-SSO-06-20230317-064023.png](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/AWS-SSO-06-20230317-064023.png) +AWS-SSO-06-20230317-064023.png
1. In the application page, open Actions > Edit attribute mappings at the top right. @@ -56,7 +56,7 @@ Click `Save changes`. ### Configure AWS IAM Identity Center integration in QueryPie
-![Administrator > General > User Management > Authentication ](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/image-20240723-072112.png) +Administrator > General > User Management > Authentication
Administrator > General > User Management > Authentication
@@ -72,7 +72,7 @@ Administrator > General > User Management > Authentication ### Sign in to QueryPie with SAML
-![image-20251020-044838.png](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/image-20251020-044838.png) +image-20251020-044838.png
Click `Login with SAML` on the login page to authenticate with AWS and sign in to QueryPie. diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx index 76c51cad..1a2aa366 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx @@ -11,7 +11,7 @@ By registering the Client ID and Client Secret created in Google Cloud API, you ### Google Cloud API Integration
-![Google Cloud API Integration for using OAuth 2.0 authentication](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-090507.png) +Google Cloud API Integration for using OAuth 2.0 authentication
Google Cloud API Integration for using OAuth 2.0 authentication
@@ -23,14 +23,14 @@ Google Cloud API Integration for using OAuth 2.0 authentication 2. Under Authentication, click the Google Cloud API tile. 3. `+Add` Click the button in the OAuth 2.0 Client IDs section.
- ![Add Client ID](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-102818.png) + Add Client ID
Add Client ID
4. Enter the information in the popup and click Save.
- ![Enter OAuth 2.0 Client ID information](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-103102.png) + Enter OAuth 2.0 Client ID information
Enter OAuth 2.0 Client ID information
@@ -48,14 +48,14 @@ Google Cloud API Integration for using OAuth 2.0 authentication 1. Check the specific Client ID you want to delete in the list.
- ![Delete Client ID](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-110050.png) + Delete Client ID
Delete Client ID
2. Click the Delete button at the top to remove it.
If the Client ID you are trying to delete is linked to a connection configuration, a warning message will appear and deletion will be blocked. First remove the OAuth settings from the connection configuration or delete the connection, then try again.
- ![Warning displayed when attempting to delete a Client ID in use by a connection](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-105240.png) + Warning displayed when attempting to delete a Client ID in use by a connection
Warning displayed when attempting to delete a Client ID in use by a connection
diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-with-email.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-with-email.mdx index 2d58fb90..eac9d967 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-with-email.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-with-email.mdx @@ -22,7 +22,7 @@ An SMTP server is required for email sending, and QueryPie provides methods for 2. Click on the Email tile to go to the details page. 3. `Configure` Click the button on the details page to display a popup for entering SMTP information.

- ![Email Integration details page](/administrator-manual/general/system/integrations/integrating-with-email/image-20241218-163108.png) + Email Integration details page
Email Integration details page
@@ -43,7 +43,7 @@ An SMTP server is required for email sending, and QueryPie provides methods for 11. **Test button**: Verifies that the SMTP settings can connect without issues.
12.
- ![SMTP settings popup dialog](/administrator-manual/general/system/integrations/integrating-with-email/image-20241218-163449.png) + SMTP settings popup dialog
SMTP settings popup dialog
@@ -56,7 +56,7 @@ An SMTP server is required for email sending, and QueryPie provides methods for 2. Click on the Email tile to go to the details page. 3. Click the Edit button for the SMTP settings displayed in Email sender on the details page.

- ![Email Sender](/administrator-manual/general/system/integrations/integrating-with-email/image-20241219-011621.png) + Email Sender
Email Sender
@@ -69,7 +69,7 @@ An SMTP server is required for email sending, and QueryPie provides methods for 2. Click on the Email tile to go to the details page. 3. Check the Sent Email History list.
Email sending history stored in this list is retained for 30 days and content older than 30 days is deleted.

- ![Sent Email History](/administrator-manual/general/system/integrations/integrating-with-email/image-20241219-005544.png) + Sent Email History
Sent Email History
@@ -81,7 +81,7 @@ An SMTP server is required for email sending, and QueryPie provides methods for 2. Click on the Email tile to go to the details page. 3. Click the Delete button for the SMTP settings displayed in Email sender on the details page.
If there are settings using the SMTP settings such as Alert, MFA, etc., the SMTP settings cannot be deleted.
All related settings must be deleted first before deletion is possible.
- ![Email Sender](/administrator-manual/general/system/integrations/integrating-with-email/image-20241219-011621.png) + Email Sender
Email Sender
diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx index 997f957e..d00a5361 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx @@ -17,7 +17,7 @@ This allows you to integrate and manage critical system event notifications with 3. Click `+ Create` on the details page to open the popup for creating an Event Callback.
-![Event Callback Integration detail page](/administrator-manual/general/system/integrations/integrating-with-event-callback/Screenshot-2025-08-25-at-6.04.50-PM.png) +Event Callback Integration detail page
Event Callback Integration detail page
@@ -38,7 +38,7 @@ Event Callback Integration detail page * **Authorization Header** : Enter the authorization header used for securing webhook requests. (e.g., Authorization: Bearer <token>) * **Description** : Enter a description for this configuration (optional).
- ![Event Callback settings popup dialog](/administrator-manual/general/system/integrations/integrating-with-event-callback/Screenshot-2025-08-25-at-6.06.50-PM.png) + Event Callback settings popup dialog
Event Callback settings popup dialog
@@ -61,6 +61,6 @@ Event Callback Integration detail page 3. In the list of created Event Callbacks, check the box to the left of the item you want to delete. 4. Click `Delete` at the top-left of the list.
- ![Screenshot-2025-08-25-at-6.14.27-PM.png](/administrator-manual/general/system/integrations/integrating-with-event-callback/Screenshot-2025-08-25-at-6.14.27-PM.png) + Screenshot-2025-08-25-at-6.14.27-PM.png
5. When the confirmation window appears, proceed to delete to remove the configuration. diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx index 3c35d007..bd073012 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx @@ -42,7 +42,7 @@ For detailed information, please refer to the Security l Secret Store configurat ### Viewing HashiCorp Vault Integration Information
-![Administrator > General > System > Integrations > HashiCorp Vault](/administrator-manual/general/system/integrations/integrating-with-secret-store/screenshot-20240723-094426.png) +Administrator > General > System > Integrations > HashiCorp Vault
Administrator > General > System > Integrations > HashiCorp Vault
@@ -59,7 +59,7 @@ To disable Secret Store activation in the Administrator > General > Securi The following is how to delete integration information.
-![Administrator > General > System > Integrations > HashiCorp Vault > Delete](/administrator-manual/general/system/integrations/integrating-with-secret-store/screenshot-20240723-095912.png) +Administrator > General > System > Integrations > HashiCorp Vault > Delete
Administrator > General > System > Integrations > HashiCorp Vault > Delete
@@ -73,7 +73,7 @@ Administrator > General > System > Integrations > HashiCorp Vault &g ### Entering HashiCorp Vault Integration Information
-![Administrator > General > System > Integrations > HashiCorp Vault > Connect](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-05-27-at-11.37.33-AM.png) +Administrator > General > System > Integrations > HashiCorp Vault > Connect
Administrator > General > System > Integrations > HashiCorp Vault > Connect
@@ -111,7 +111,7 @@ Administrator > General > System > Integrations > HashiCorp Vault &g ### Viewing Active Directory Integration Information
-![Administrator > General > System > Integrations > Microsoft Active Directory](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-07-22-at-11.32.23-AM.png) +Administrator > General > System > Integrations > Microsoft Active Directory
Administrator > General > System > Integrations > Microsoft Active Directory
@@ -125,7 +125,7 @@ Administrator > General > System > Integrations > Microsoft Active D ### Deleting Active Directory Integration Information
-![Screenshot-2025-07-22-at-11.33.43-AM.png](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-07-22-at-11.33.43-AM.png) +Screenshot-2025-07-22-at-11.33.43-AM.png
1. Select the checkbox for the AD information item you want to delete in the table, and a `Delete` button will appear in the header area. Click that button. @@ -142,7 +142,7 @@ Please proceed with the following procedure after deleting all related accounts ### Entering Active Directory Integration Information
-![Screenshot-2025-07-22-at-11.33.26-AM.png](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-07-22-at-11.33.26-AM.png) +Screenshot-2025-07-22-at-11.33.26-AM.png
1. Click the `+ Connect` button on the Active Directory page. diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx index 71e405a4..cc1bee37 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx @@ -27,15 +27,15 @@ Create a Slack App dedicated for QueryPie DM integration using App Manifest. 1. [https://api.slack.com/apps](https://api.slack.com/apps) and click `Create an App`.

- ![image-20231227-065658.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20231227-065658.png) + image-20231227-065658.png
2. In the Create an app modal, select the app creation method. Click `From a manifest`.

- ![screenshot-20250218-131725.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-131725.png) + screenshot-20250218-131725.png
3. In the Pick a workspace modal, select the Slack Workspace to integrate with QueryPie and proceed to the next step.

- ![image-20231227-065951.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20231227-065951.png) + image-20231227-065951.png
4. In the Create app from manifest modal, enter the App Manifest in JSON format.
Delete the pre-filled content and paste the App Manifest below, then proceed to the next step.
:light_bulb_on: Please change the values in `{{..}}` to your desired values.
``` @@ -70,7 +70,7 @@ Create a Slack App dedicated for QueryPie DM integration using App Manifest. ``` 5. Review the settings and click the `Create` button to complete app creation.

- ![image-20240115-220447.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240115-220447.png) + image-20240115-220447.png
### Installing Slack App in Slack Workspace @@ -78,11 +78,11 @@ Create a Slack App dedicated for QueryPie DM integration using App Manifest. 1. In Settings > Install App, click the `Install to Workspace` button to install the created app in the Slack Workspace. 2. On the permission request page, click `Allow`.
- ![image-20240115-221520.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240115-221520.png) + image-20240115-221520.png
3. You can confirm that a Slack DM dedicated app has been created in the configured Slack Workspace.
- ![image-20240115-221618.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240115-221618.png) + image-20240115-221618.png
### Obtaining Bot User OAuth Token @@ -90,7 +90,7 @@ Create a Slack App dedicated for QueryPie DM integration using App Manifest. In the OAuth Tokens for Your Workspace section of the Features > OAuth & Permissions menu, copy and record the **Bot User OAuth Token**.
-![image-20240418-022640.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240418-022640.png) +image-20240418-022640.png
@@ -106,11 +106,11 @@ Follow these steps to manually create an App-Level Token. 1. Go to the App-Level Tokens section in Settings > Basic Information menu of the app settings page and click the `Generate Token and Scope` button.

- ![screenshot-20250218-140951.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-140951.png) + screenshot-20250218-140951.png
2. In the Generate an app-level token modal, click the Add Scope button and add `connections:write`.

- ![screenshot-20250218-141555.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-141555.png) + screenshot-20250218-141555.png
3. In the generated App-Level Token modal, copy the app token and record it separately. App-Level Token starts with `xapp-`. @@ -118,7 +118,7 @@ Follow these steps to manually create an App-Level Token. 1. Navigate to Admin > General > System > Integrations > Slack menu and click the `Configure` button to open the settings modal.

- ![Administrator > General > System > Integrations > Slack > Create a New Slack Configuration](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250310-113509.png) + Administrator > General > System > Integrations > Slack > Create a New Slack Configuration
Administrator > General > System > Integrations > Slack > Create a New Slack Configuration
@@ -128,7 +128,7 @@ Follow these steps to manually create an App-Level Token. * **Send Workflow Notification via Slack DM** : Enable Slack DM sending for workflow requests * **Allow Users to approve or reject on Slack DM** : Enable approval or rejection functionality within Slack DM

- ![Action-enabled type example (left) / Action-disabled type example (right)](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20231003-054240.png) + Action-enabled type example (left) / Action-disabled type example (right)
Action-enabled type example (left) / Action-disabled type example (right)
@@ -139,14 +139,14 @@ Follow these steps to manually create an App-Level Token. 1. After registering Slack Configuration, you can check the current settings status on the screen.

- ![Administrator > General > System > Integrations > Slack](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250310-113950.png) + Administrator > General > System > Integrations > Slack
Administrator > General > System > Integrations > Slack
2. `Edit` button to modify the entered settings.
- ![Administrator > General > System > Integrations > Slack > Edit the Slack Configuration](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-152840.png) + Administrator > General > System > Integrations > Slack > Edit the Slack Configuration
Administrator > General > System > Integrations > Slack > Edit the Slack Configuration
@@ -159,13 +159,13 @@ Using DB Access Request as an example, test whether the Slack DM functionality w 1. In QueryPie User > Workflow page, click the Submit Request button, select DB Access Request to enter the request creation screen. Enter the necessary information in the request creation screen and submit the request.
- ![screenshot-20250218-151504.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-151504.png) + screenshot-20250218-151504.png
2. Approvers can receive notifications for requests that need approval via DM with the Slack App added earlier.
**Allow Users to approve or reject on Slack DM** is enabled, you can directly enter reasons in DM and approve or reject requests.

- ![screenshot-20250218-152238.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-152238.png) + screenshot-20250218-152238.png
3. When clicking the `Details` button in DM, you can view detailed content about the approval request in QueryPie Admin and approve or reject it.
- ![screenshot-20250218-152527.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-152527.png) + screenshot-20250218-152527.png
diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx index 5b1de24a..67237f6a 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx @@ -44,7 +44,7 @@ For post-approval (Urgent Mode) drafts, the fact is also included in the message Since it's a post-approval request, only the `Approve` button appears even when using action buttons.
-![Normal Mode Approval Request Example (Left) / Post-Approval Mode Approval Request Example (Right)](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-062427.png) +Normal Mode Approval Request Example (Left) / Post-Approval Mode Approval Request Example (Right)
Normal Mode Approval Request Example (Left) / Post-Approval Mode Approval Request Example (Right)
@@ -53,7 +53,7 @@ Normal Mode Approval Request Example (Left) / Post-Approval Mode Approval Reques ### Rejection Notification
-![image-20231003-060544.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-060544.png) +image-20231003-060544.png
Supports all four types of Workflows (SQL Request, SQL Export Request, DB Access Request, Server Access Request). @@ -70,7 +70,7 @@ Therefore, rejection messages also do not exist. ### Approval Completion Notification - to Requester
-![image-20231003-060552.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-060552.png) +image-20231003-060552.png
Supports all four types of Workflows (SQL Request, SQL Export Request, DB Access Request, Server Access Request). @@ -96,13 +96,13 @@ On this page, you can execute SQL Request and SQL Export Request. For post-approval (Urgent Mode) drafts, a message is sent to the executor immediately upon draft submission.
-![image-20231003-062055.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-062055.png) +image-20231003-062055.png
### Urgent Mode Unapproved Notification
-![image-20231003-062615.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-062615.png) +image-20231003-062615.png
Supports two types (SQL Request, SQL Export Request) in Workflow. diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-with-splunk.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-with-splunk.mdx index 312e692d..cecc8c36 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-with-splunk.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-with-splunk.mdx @@ -18,7 +18,7 @@ System admin privileges are required for Integration settings. ### Recommended Syslog-Splunk Integration Architecture
-![Recommended Splunk Integration Architecture](/administrator-manual/general/system/integrations/integrating-with-splunk/screenshot-20240613-174947.png) +Recommended Splunk Integration Architecture
Recommended Splunk Integration Architecture
@@ -43,7 +43,7 @@ For reference, Splunk provides SC4S (Splunk connector for syslog) separately for 3. Click the `Configure` button on the detail page to display a popup where you can enter Destination information.
-![(Left) TCP / UDP Settings Screen (Right) HTTP / HTTPS Settings Screen](/administrator-manual/general/system/integrations/integrating-with-splunk/image-20240523-101104.png) +(Left) TCP / UDP Settings Screen (Right) HTTP / HTTPS Settings Screen
(Left) TCP / UDP Settings Screen (Right) HTTP / HTTPS Settings Screen
@@ -84,7 +84,7 @@ Additionally, streaming transmission functionality for events generated by the N
-![image-20251009-045210.png](/administrator-manual/general/system/integrations/integrating-with-splunk/image-20251009-045210.png) +image-20251009-045210.png
diff --git a/src/content/en/administrator-manual/general/system/integrations/integrating-with-syslog.mdx b/src/content/en/administrator-manual/general/system/integrations/integrating-with-syslog.mdx index 826f3906..c17ee8f9 100644 --- a/src/content/en/administrator-manual/general/system/integrations/integrating-with-syslog.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/integrating-with-syslog.mdx @@ -29,7 +29,7 @@ The default is UTC. 1. Click the `Configure` button on the detail page to display a popup where you can enter Destination information.
-![Administrator > General > System > Integrations > Syslog > Configure Destination](/administrator-manual/general/system/integrations/integrating-with-syslog/screenshot-20240723-093628.png) +Administrator > General > System > Integrations > Syslog > Configure Destination
Administrator > General > System > Integrations > Syslog > Configure Destination
@@ -60,7 +60,7 @@ Additionally, streaming transmission functionality for events generated by the N
-![image-20251009-045004.png](/administrator-manual/general/system/integrations/integrating-with-syslog/image-20251009-045004.png) +image-20251009-045004.png
diff --git a/src/content/en/administrator-manual/general/system/integrations/oauth-client-application.mdx b/src/content/en/administrator-manual/general/system/integrations/oauth-client-application.mdx index 68beb86a..a69b29f2 100644 --- a/src/content/en/administrator-manual/general/system/integrations/oauth-client-application.mdx +++ b/src/content/en/administrator-manual/general/system/integrations/oauth-client-application.mdx @@ -12,7 +12,7 @@ You can register external applications as clients, and QueryPie issues tokens to ### Register an OAuth Client Application
-![OAuth Client Application under Admin > General > System > Integrations, Authentication section](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-041209.png) +OAuth Client Application under Admin > General > System > Integrations, Authentication section
OAuth Client Application under Admin > General > System > Integrations, Authentication section
@@ -26,7 +26,7 @@ OAuth Client Application under Admin > General > System > Integrations, * **Refresh Token Timeout (Minutes)** : Default 1440, minimum 5.
-![Add OAuth Client Application](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-043210.png) +Add OAuth Client Application
Add OAuth Client Application
@@ -36,7 +36,7 @@ Add OAuth Client Application * After saving, a popup shows the Client ID and Client Secret. Since the Client Secret cannot be retrieved again, copy and store it securely.
-![Client ID and Client Secret](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-043334.png) +Client ID and Client Secret
Client ID and Client Secret
@@ -45,7 +45,7 @@ Client ID and Client Secret ### Edit OAuth Client Application settings
-![Edit OAuth Client Application](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-044214.png) +Edit OAuth Client Application
Edit OAuth Client Application
@@ -61,7 +61,7 @@ In the OAuth Client Application list, click a row to: To delete a configured OAuth Client Application, select the item in the list and click `Delete`.
-![Delete OAuth Client Application](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-044400.png) +Delete OAuth Client Application
Delete OAuth Client Application
diff --git a/src/content/en/administrator-manual/general/system/jobs.mdx b/src/content/en/administrator-manual/general/system/jobs.mdx index f69aab2f..e90049e1 100644 --- a/src/content/en/administrator-manual/general/system/jobs.mdx +++ b/src/content/en/administrator-manual/general/system/jobs.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' This is a menu that provides an overview of various tasks that run periodically or manually on the QueryPie system.
-![Administrator > General > System > Jobs](/administrator-manual/general/system/jobs/screenshot-20241107-223755.png) +Administrator > General > System > Jobs
Administrator > General > System > Jobs
@@ -52,7 +52,7 @@ Information displayed for each job is as follows.
-![Administrator > General > System > Jobs > List Detail](/administrator-manual/general/system/jobs/screenshot-20241107-223800.png) +Administrator > General > System > Jobs > List Detail
Administrator > General > System > Jobs > List Detail
@@ -83,7 +83,7 @@ As of version 10.2.0, Total, Success, Failure, Ignored information is only provi ### Viewing Job History
-![Administrator > General > System > Jobs > List Detail > History Detail](/administrator-manual/general/system/jobs/screenshot-20241107-223901.png) +Administrator > General > System > Jobs > List Detail > History Detail
Administrator > General > System > Jobs > List Detail > History Detail
diff --git a/src/content/en/administrator-manual/general/system/maintenance.mdx b/src/content/en/administrator-manual/general/system/maintenance.mdx index 17e6c260..ae3b776c 100644 --- a/src/content/en/administrator-manual/general/system/maintenance.mdx +++ b/src/content/en/administrator-manual/general/system/maintenance.mdx @@ -32,7 +32,7 @@ Since this affects the entire service, decide carefully and proceed with caution
-![Admin > General > System > Maintenance](/administrator-manual/general/system/maintenance/image-20250928-205515.png) +Admin > General > System > Maintenance
Admin > General > System > Maintenance
diff --git a/src/content/en/administrator-manual/general/user-management.mdx b/src/content/en/administrator-manual/general/user-management.mdx index e6015aa4..cf480624 100644 --- a/src/content/en/administrator-manual/general/user-management.mdx +++ b/src/content/en/administrator-manual/general/user-management.mdx @@ -9,7 +9,7 @@ title: 'User Management' The User Management menu provides various features for managing QueryPie users, administrators, and user groups.
-![Administrator > General > Company Management > Security](/administrator-manual/general/user-management/screenshot-20240726-175124.png) +Administrator > General > Company Management > Security
Administrator > General > Company Management > Security
diff --git a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx index 50508dcd..05649352 100644 --- a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx +++ b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx @@ -12,7 +12,7 @@ You can grant access permissions and apply policies by synchronizing users. ### Adding QueryPie as an Application in AWS IAM Identity Center
-![AWS-SSO-01-20230317-044219.png](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/AWS-SSO-01-20230317-044219.png) +AWS-SSO-01-20230317-044219.png
1. Access [AWS IAM Identity Center](https://ap-northeast-2.console.aws.amazon.com/singlesignon/applications/home). @@ -31,7 +31,7 @@ You can grant access permissions and apply policies by synchronizing users. ### Setting Attribute Mapping for QueryPie Integration
-![AWS-SSO-06-20230317-064023.png](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/AWS-SSO-06-20230317-064023.png) +AWS-SSO-06-20230317-064023.png
1. Go to Actions > Edit Attribute Mapping in the top right corner of the created application. @@ -50,7 +50,7 @@ Click the `Save Changes` button to save. ### Configuring AWS IAM Identity Center Integration in QueryPie
-![Administrator > General > User Management > Authentication ](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/image-20240723-072112.png) +Administrator > General > User Management > Authentication
Administrator > General > User Management > Authentication
@@ -65,7 +65,7 @@ Administrator > General > User Management > Authentication ### SAML Login in QueryPie
-![image-20240723-073353.png](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/image-20240723-073353.png) +image-20240723-073353.png
Now you can authenticate with AWS and log in to QueryPie through the `Login with SAML` button on the login page. diff --git a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx index fb3f6229..ca387243 100644 --- a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx +++ b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx @@ -15,14 +15,14 @@ You can grant access permissions and apply policies by synchronizing users. 1. Access the Google Admin Console homepage and click Apps > `Web and mobile apps` in the left menu.
-![screenshot-20240902-162650.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-162650.png) +screenshot-20240902-162650.png
2. Click the `Add App` button and then click `Add Custom SAML App`.
-![image-20240902-073821.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/image-20240902-073821.png) +image-20240902-073821.png
@@ -30,7 +30,7 @@ You can grant access permissions and apply policies by synchronizing users. Enter 'QueryPie-SSO' in the App Name field and click the `Continue` button.
-![screenshot-20240902-164038.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164038.png) +screenshot-20240902-164038.png
@@ -38,7 +38,7 @@ Enter 'QueryPie-SSO' in the App Name field and click the `Continue` button. After entering, click the `Continue` button to proceed to step 3.
-![screenshot-20240902-164356.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164356.png) +screenshot-20240902-164356.png
* ACS URL : `https://{QueryPie Host}/saml/sp/acs` @@ -49,7 +49,7 @@ After entering, click the `Continue` button to proceed to step 3. 5. On the step 3 page, click the `Add Mapping` button, enter all four values below, and click the `Finish` button.
-![screenshot-20240902-164739.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164739.png) +screenshot-20240902-164739.png
* Basic Information : Primary email → email @@ -61,7 +61,7 @@ After entering, click the `Continue` button to proceed to step 3. 6. Enter your Google authentication password and click `Next` to complete creation.
-![screenshot-20240902-164955.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164955.png) +screenshot-20240902-164955.png
@@ -69,21 +69,21 @@ After entering, click the `Continue` button to proceed to step 3. Click on the app to enable it.
-![screenshot-20240902-165202.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-165202.png) +screenshot-20240902-165202.png
8. In the app details, click `Download Metadata` to download the file, then click the `User Access` item.
-![screenshot-20240902-165512.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-165512.png) +screenshot-20240902-165512.png
9. Select 'Enable for all users' in Service Status and click the `Save` button.
-![screenshot-20240902-165647.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-165647.png) +screenshot-20240902-165647.png
@@ -92,7 +92,7 @@ Click on the app to enable it. 1. Navigate to QueryPie Admin > General > User Management > Authentication menu and configure as follows.
-![screenshot-20240902-170029.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-170029.png) +screenshot-20240902-170029.png
* Type : Select SAML. @@ -103,7 +103,7 @@ Click on the app to enable it. ### SAML Login in QueryPie
-![image-20240723-073353.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/image-20240723-073353.png) +image-20240723-073353.png
Now you can authenticate with Google and log in to QueryPie through the `Login with SAML` button on the login page. diff --git a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx index 051a54bf..5de5ffcd 100644 --- a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx +++ b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx @@ -20,7 +20,7 @@ Navigate to Administrator > General > User Management > Authentication
-![Administrator > General > User Management > Authentication > LDAP](/administrator-manual/general/user-management/authentication/integrating-with-ldap/screenshot-20241209-203250.png) +Administrator > General > User Management > Authentication > LDAP
Administrator > General > User Management > Authentication > LDAP
@@ -29,7 +29,7 @@ Administrator > General > User Management > Authentication > LDAP #### Basic User Integration Configuration
-![image-20250515-095143.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20250515-095143.png) +image-20250515-095143.png
Enter basic authentication information and attribute information for LDAP integration. @@ -39,7 +39,7 @@ For detailed descriptions, please refer to the items below. #### Group Integration Configuration
-![image-20250515-095109.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20250515-095109.png) +image-20250515-095109.png
To synchronize user group information and membership information from LDAP, activate the **Use Group option** and enter the required information. @@ -125,7 +125,7 @@ Enter the attribute value to use as the group identifier. To execute user information synchronization from LDAP server, activate the **Use Synchronization with the Authentication System** option.
-![image-20250515-095420.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20250515-095420.png) +image-20250515-095420.png
* **Replication Frequency** : Sets whether to use automatic synchronization functionality. @@ -227,7 +227,7 @@ After completing mapping and performing synchronization, linked Attributes can b * **Dry Run :** Clicking the `Dry Run` button allows you to preview the results if synchronization is performed based on the currently entered configuration information. (Regardless of whether the currently entered information is saved) * Clicking `Save Changes` saves the entered configuration information to QueryPie. * Clicking the `Synchronize` button performs synchronization based on the currently entered configuration information. (Only activated after saving the currently entered configuration information) - * ![image-20241209-124345.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20241209-124345.png)Clicking the button allows you to view the previous synchronization history. + * image-20241209-124345.png버튼을 클릭하면 직전의 동기화 이력을 조회할 수 있습니다. * If there are failed items during individual synchronization, the Progress Bar color is displayed in yellow. * Failure logs are displayed with ❌ icon. Clicking the log allows you to check detailed error messages. @@ -243,14 +243,14 @@ After completing mapping and performing synchronization, linked Attributes can b 1. You can check synchronized users and groups in Administrator > General > User Management > Users or Groups menu.
- ![Admin > General > User Management > Users](/administrator-manual/general/user-management/authentication/integrating-with-ldap/screenshot-20241209-215940.png) + Admin > General > User Management > Users
Admin > General > User Management > Users
2. Now you can log in by entering LDAP authentication information in the ID and Password fields on the login page.
- ![QueryPie Log In](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20240723-063737.png) + QueryPie Log In
QueryPie Log In
diff --git a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx index 9527b1f0..8485396a 100644 --- a/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx +++ b/src/content/en/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx @@ -20,7 +20,7 @@ If you also plan to implement SCIM provisioning integration, please follow the s ### Add QueryPie as an application in Okta
-![Okta Admin > Applications > Applications > Browse App Catalog > Search QueryPie](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-064242.png) +Okta Admin > Applications > Applications > Browse App Catalog > Search QueryPie
Okta Admin > Applications > Applications > Browse App Catalog > Search QueryPie
@@ -37,7 +37,7 @@ Okta Admin > Applications > Applications > Browse App Catalog > Sear ### Profile settings for Okta account integration
-![Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-064424.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
@@ -53,7 +53,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Add Attrib 4. Display name: loginId / Variable name: loginId, then click `Save`
-![Okta Admin > Directory > Profile Editor > QueryPie User > Mappings](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-064721.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
@@ -71,7 +71,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Mappings ### Assign users to the QueryPie application added in Okta
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-065134.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -89,7 +89,7 @@ Okta Admin > Applications > Applications > QueryPie App ### Configure integration information for the QueryPie application in Okta
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-065346.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -112,7 +112,7 @@ Typically, you can generate an API token using a Super Administrator or Read-Onl However, to enhance security by minimizing permissions for the Okta API token, we recommend creating a token with the following roles and steps:
-![Okta Admin Console > Security > Administrators > Roles > Create new role](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240110-042233.png) +Okta Admin Console > Security > Administrators > Roles > Create new role
Okta Admin Console > Security > Administrators > Roles > Create new role
@@ -151,7 +151,7 @@ Okta Admin Console > Security > Administrators > Roles > Create new ### Configure Okta integration and synchronization in QueryPie
-![Administrator > General > User Management > Authentication](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20241103-071714.png) +Administrator > General > User Management > Authentication
Administrator > General > User Management > Authentication
@@ -176,7 +176,7 @@ If you use two or more QueryPie applications, go to Okta Admin > Applications
-![Okta Admin > Applications > QueryPie App URL at the top](/administrator-manual/general/user-management/authentication/integrating-with-okta/Authentication-Okta-02.png) +Okta Admin > Applications > QueryPie App URL at the top
Okta Admin > Applications > QueryPie App URL at the top
@@ -189,7 +189,7 @@ Okta Admin > Applications > QueryPie App URL at the top 2. You can now log in to QueryPie with your Okta account by clicking the `Login with Okta` button on the sign-in page.
-![image-20240723-070449.png](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-070449.png) +image-20240723-070449.png
diff --git a/src/content/en/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx b/src/content/en/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx index dd152436..a3b8a0d6 100644 --- a/src/content/en/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx +++ b/src/content/en/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx @@ -23,14 +23,14 @@ To specify MFA method, Authentication Type must be set to Internal database or L * Navigate to Admin > General > User Management > Authentication. * When Authentication Type is Internal database

- ![MFA Settings for Authentication Type - Internal Database](/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication/image-20241219-015811.png) + MFA Settings for Authentication Type - Internal Database
MFA Settings for Authentication Type - Internal Database
* When Authentication Type is LDAP


- ![MFA Settings for Authentication Type - LDAP](/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication/image-20241219-020050.png) + MFA Settings for Authentication Type - LDAP
MFA Settings for Authentication Type - LDAP
@@ -45,7 +45,7 @@ This setting can only be used when Server Access Control (SAC) license is activa * Navigate to Admin > General > Company Management > Security. * Set Access Server with MFA under Server Connection Security to "Enable" and select Google OTP or Email as MFA Type. (Access Server with MFA has a default value of Disable.

- ![image-20241219-021137.png](/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication/image-20241219-021137.png) + image-20241219-021137.png
diff --git a/src/content/en/administrator-manual/general/user-management/groups.mdx b/src/content/en/administrator-manual/general/user-management/groups.mdx index e900a478..2efa19a7 100644 --- a/src/content/en/administrator-manual/general/user-management/groups.mdx +++ b/src/content/en/administrator-manual/general/user-management/groups.mdx @@ -20,7 +20,7 @@ You can search by group name. The viewable information is as follows:
-![Administrator > General > User Management > Groups](/administrator-manual/general/user-management/groups/image-20240714-053938.png) +Administrator > General > User Management > Groups
Administrator > General > User Management > Groups
@@ -50,7 +50,7 @@ User addition or deletion is only possible for manually added groups.
For gr Click on the group you want to add users to in the list to open a Drawer where you can view detailed information.
-![Administrator > General > User Management > Groups > Details](/administrator-manual/general/user-management/groups/screenshot-20240726-121151.png) +Administrator > General > User Management > Groups > Details
Administrator > General > User Management > Groups > Details
@@ -62,7 +62,7 @@ Administrator > General > User Management > Groups > Details 3. Click on the user you want to add to change to added status. 4. Click the `Check all` button at the bottom to select all users.
- ![Adding users to group](/administrator-manual/general/user-management/groups/image-20251009-050919.png) + Adding users to group
Adding users to group
@@ -83,7 +83,7 @@ Check in the Users page whether the user's account status is Inactive. 3. When user removal is complete, you can verify it in the user list within the Drawer and the Group list.
-![Administrator > General > User Management > Groups > Details](/administrator-manual/general/user-management/groups/screenshot-20240726-122800.png) +Administrator > General > User Management > Groups > Details
Administrator > General > User Management > Groups > Details
@@ -96,7 +96,7 @@ Click the `Edit` button at the top of the group details Drawer to display the ed Change the group name and click the `Save` button to save.
-![Administrator > General > User Management > Groups > Details > Update Group](/administrator-manual/general/user-management/groups/screenshot-20240726-122036.png) +Administrator > General > User Management > Groups > Details > Update Group
Administrator > General > User Management > Groups > Details > Update Group
@@ -110,7 +110,7 @@ The `Delete` button appears in the table header. Click the button and click the `OK` button in the confirmation modal to complete deletion.
-![screenshot-20240726-123314.png](/administrator-manual/general/user-management/groups/screenshot-20240726-123314.png) +screenshot-20240726-123314.png
diff --git a/src/content/en/administrator-manual/general/user-management/profile-editor.mdx b/src/content/en/administrator-manual/general/user-management/profile-editor.mdx index 79ce7d05..b861d64d 100644 --- a/src/content/en/administrator-manual/general/user-management/profile-editor.mdx +++ b/src/content/en/administrator-manual/general/user-management/profile-editor.mdx @@ -14,7 +14,7 @@ Additionally, not only predefined attributes but also custom attributes can be c This enables flexible user information management tailored to each organization's policies.
-![Screenshot-2025-05-09-at-2.04.57-PM.png](/administrator-manual/general/user-management/profile-editor/Screenshot-2025-05-09-at-2.04.57-PM.png) +Screenshot-2025-05-09-at-2.04.57-PM.png
### User Attribute Authority Setting Definition diff --git a/src/content/en/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx b/src/content/en/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx index 24fee123..06ff81d1 100644 --- a/src/content/en/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx +++ b/src/content/en/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx @@ -12,24 +12,24 @@ This document provides guidance on Custom Attribute configuration and management 1. Click the `+ Create Attribute` button in the top right corner of the attribute list table.
- ![Administrator > General > User Management > Profile Editor](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.04.57-PM.png) + Administrator > General > User Management > Profile Editor
Administrator > General > User Management > Profile Editor
2. Enter the items specified below and click the `OK` button to create a Custom Attribute.
- ![Screenshot-2025-05-09-at-2.23.22-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.23.22-PM.png) + Screenshot-2025-05-09-at-2.23.22-PM.png
* **Display Name** (Required): Name of the attribute that cannot be duplicated. Example) Team Leader * When Display Name is duplicated, the following error message is displayed in a modal.
- ![Screenshot-2025-05-09-at-2.43.56-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.43.56-PM.png) + Screenshot-2025-05-09-at-2.43.56-PM.png
* **Variable Name** (Required): Variable name of the attribute that cannot be duplicated. Example) teamLeader * When Variable Name is duplicated, the following error message is displayed in a modal.
- ![Screenshot-2025-05-09-at-2.45.22-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.45.22-PM.png) + Screenshot-2025-05-09-at-2.45.22-PM.png
* **Datatype** (Required): Select the data type of the attribute value. * string: General text (string) value. (Example: "Marketing Team") @@ -62,7 +62,7 @@ This document provides guidance on Custom Attribute configuration and management 1. Deletion method:
- ![Screenshot-2025-05-09-at-2.36.41-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.36.41-PM.png) + Screenshot-2025-05-09-at-2.36.41-PM.png
* Select the checkbox of the Custom Attribute item to delete. * Click the `Delete` button that appears at the top of the table. diff --git a/src/content/en/administrator-manual/general/user-management/provisioning.mdx b/src/content/en/administrator-manual/general/user-management/provisioning.mdx index d99d2589..6561fbed 100644 --- a/src/content/en/administrator-manual/general/user-management/provisioning.mdx +++ b/src/content/en/administrator-manual/general/user-management/provisioning.mdx @@ -10,7 +10,7 @@ title: 'Provisioning' By integrating with the account system used by your organization, you can synchronize Attributes (attributes) and status corresponding to users and groups within your organization to QueryPie immediately as they are reflected in the account system.
-![screenshot-20240613-174843.png](/administrator-manual/general/user-management/provisioning/screenshot-20240613-174843.png) +screenshot-20240613-174843.png
@@ -20,7 +20,7 @@ QueryPie defines user ledgers based on the Auth Provider field. This Auth Provider follows the external account system type configured in the Administrator > General > User Management > Authentication menu.
-![Administrator > General > User Management > Provisioning](/administrator-manual/general/user-management/provisioning/image-20240714-054222.png) +Administrator > General > User Management > Provisioning
Administrator > General > User Management > Provisioning
diff --git a/src/content/en/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx b/src/content/en/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx index 6b68e3a1..da8ef7d3 100644 --- a/src/content/en/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx +++ b/src/content/en/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx @@ -22,7 +22,7 @@ By supporting user lifecycle management, administrators can more conveniently ma ### Activating QueryPie Provisioning
-![Administrator > General > User Management > Provisioning](/administrator-manual/general/user-management/provisioning/activating-provisioning/image-20240714-054222.png) +Administrator > General > User Management > Provisioning
Administrator > General > User Management > Provisioning
diff --git a/src/content/en/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx b/src/content/en/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx index 3c90bad5..8a436919 100644 --- a/src/content/en/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx +++ b/src/content/en/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx @@ -40,7 +40,7 @@ ______ #### Create an Okta custom SCIM app
-![Okta Admin Console > Applications > Applications > Create App Integration > SAML 2.0 > Configure SAML](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240723-050205.png) +Okta Admin Console > Applications > Applications > Create App Integration > SAML 2.0 > Configure SAML
Okta Admin Console > Applications > Applications > Create App Integration > SAML 2.0 > Configure SAML
@@ -73,7 +73,7 @@ ______ #### Okta-QueryPie Provisioning integration
-![Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > Integration](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240723-054522.png) +Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > Integration
Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > Integration
@@ -98,7 +98,7 @@ You must complete the [Activating Provisioning](activating-provisioning) step fi 3. Click the Test Connector Configuration button to test the connection. 4. When a popup appears with the message "*Connector configured successfully*", click the `Close` button.
- ![image-20240430-025059.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-025059.png) + image-20240430-025059.png
5. Click the `Save` button at the bottom to save the connection settings. @@ -108,7 +108,7 @@ ______ #### Enable and verify SCIM API
-![Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > To App](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-034915.png) +Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > To App
Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > To App
@@ -147,36 +147,36 @@ If you need to sync these attribute information together, you can add Custom Att 1. Click `Go to Profile Editor` under Provisioning > To App in the SCIM app's Provisioning tab.
- ![image-20240712-082412.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082412.png) + image-20240712-082412.png
2. Click the `Add Attribute` button.
- ![image-20240712-082549.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082549.png) + image-20240712-082549.png
3. Register a new attribute needed for synchronization.
- ![image-20240712-082453.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082453.png) + image-20240712-082453.png
1. Data type: Select string, same as in QueryPie. 2. Display name: Enter the attribute name to display in Okta. 3. Variable name & External name: Enter the variable name of the custom attribute to synchronize. * You can also check the variable names in the QueryPie user profile (shown in parentheses).
- ![image-20240712-083117.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-083117.png) + image-20240712-083117.png
4. External namespace: Enter the following value.
`urn:ietf:params:scim:schemas:extension:querypie:2.0:User` 5. Then click the `Save` or `Save and Add Another` button to save. 4. Then click the `Mappings` button.
- ![image-20240712-082549.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082549.png) + image-20240712-082549.png
1. Select the second tab (Okta → `{APP}`) at the top of the prompt.
- ![image-20240712-083618.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-083618.png) + image-20240712-083618.png
2. Map the newly created Custom Attribute with the appropriate Attribute in IdP at the bottom and click the Save Mappings button to save the settings.
- ![image-20240712-085207.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-085207.png) + image-20240712-085207.png
5. Then assign users to the app. @@ -187,7 +187,7 @@ ______ 1. Return to the SCIM app and assign users through the options of the `Assign` button in the Assignments tab.
- ![Okta Admin Console > Applications > Applications > Custom SCIM App > Assignments](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-035937.png) + Okta Admin Console > Applications > Applications > Custom SCIM App > Assignments
Okta Admin Console > Applications > Applications > Custom SCIM App > Assignments
@@ -196,7 +196,7 @@ ______ 2. **Assign to Groups**: Assign by user group 2. Return to the QueryPie app and go to Administrator > General > User Management > Users to verify that users have been pushed successfully.
- ![Administrator > General > User Management > Users > List Details](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240723-040531.png) + Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -206,7 +206,7 @@ ______ #### Verify group provisioning
-![Okta Admin Console > Applications > Applications > Custom SCIM App > Push Groups](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-062231.png) +Okta Admin Console > Applications > Applications > Custom SCIM App > Push Groups
Okta Admin Console > Applications > Applications > Custom SCIM App > Push Groups
diff --git a/src/content/en/administrator-manual/general/user-management/roles.mdx b/src/content/en/administrator-manual/general/user-management/roles.mdx index b4f0047c..c0d7d4c7 100644 --- a/src/content/en/administrator-manual/general/user-management/roles.mdx +++ b/src/content/en/administrator-manual/general/user-management/roles.mdx @@ -34,7 +34,7 @@ You can search by name. * Administrator roles provided by default in QueryPie have Created by value marked as System.
-![Administrator > General > User Management > Roles](/administrator-manual/general/user-management/roles/screenshot-20240726-130853.png) +Administrator > General > User Management > Roles
Administrator > General > User Management > Roles
@@ -50,7 +50,7 @@ The Owner role is an administrator role that can access the entire QueryPie syst Click on the role you want to view details for in the Roles list to enter the detail page.
-![Administrator > General > User Management > Roles > List Details](/administrator-manual/general/user-management/roles/screenshot-20240726-131148.png) +Administrator > General > User Management > Roles > List Details
Administrator > General > User Management > Roles > List Details
@@ -65,7 +65,7 @@ The Detail tab displays the list of policies assigned to the administrator role 2. The modal displays a list of policies not currently assigned to that role. Click on the desired policy to add it, then click the `Assign` button to save.
-![screenshot-20240726-131834.png](/administrator-manual/general/user-management/roles/screenshot-20240726-131834.png) +screenshot-20240726-131834.png
1. You can check the list of additionally assigned policies in the administrator role detail page. @@ -78,7 +78,7 @@ Select the policy you want to remove with a checkbox in the policy list in the D Click the `OK` button in the confirmation modal to complete policy removal.
-![Administrator > General > User Management > Roles > List Details](/administrator-manual/general/user-management/roles/screenshot-20240726-132233.png) +Administrator > General > User Management > Roles > List Details
Administrator > General > User Management > Roles > List Details
@@ -90,7 +90,7 @@ Administrator > General > User Management > Roles > List Details Enter the detail page of the administrator role you want to modify in the Roles list. Click the `Edit` button to open the modification modal, where you can modify the name and description.
-![Role Modification Modal](/administrator-manual/general/user-management/roles/screenshot-20240726-132439.png) +Role Modification Modal
Role Modification Modal
@@ -105,7 +105,7 @@ Two methods are provided for deleting administrator roles that are no longer use When an administrator role is deleted, that role is immediately revoked from users who had previously been assigned that role. Administrator role deletion cannot be undone, so please execute carefully.
-![screenshot-20240726-132448.png](/administrator-manual/general/user-management/roles/screenshot-20240726-132448.png) +screenshot-20240726-132448.png
@@ -115,7 +115,7 @@ Select the role you want to delete with a checkbox in the Roles list, then click In the confirmation modal, correctly enter the deletion confirmation phrase "DELETE" and click the `Delete` button to complete administrator role deletion.
-![Administrator > General > User Management > Roles](/administrator-manual/general/user-management/roles/screenshot-20240726-132801.png) +Administrator > General > User Management > Roles
Administrator > General > User Management > Roles
@@ -126,7 +126,7 @@ Administrator > General > User Management > Roles Enter the detail page of the administrator role you want to delete in the Roles list. Click the `Delete` button to open the deletion confirmation modal, then correctly enter the deletion confirmation phrase "DELETE" and click the `Delete` button to complete administrator role deletion.
-![Administrator > General > User Management > Roles > List Details](/administrator-manual/general/user-management/roles/screenshot-20240726-133911.png) +Administrator > General > User Management > Roles > List Details
Administrator > General > User Management > Roles > List Details
diff --git a/src/content/en/administrator-manual/general/user-management/users.mdx b/src/content/en/administrator-manual/general/user-management/users.mdx index 628f47d0..6aad8d7a 100644 --- a/src/content/en/administrator-manual/general/user-management/users.mdx +++ b/src/content/en/administrator-manual/general/user-management/users.mdx @@ -16,7 +16,7 @@ The User page allows you to view the list of users currently registered in Query You can view the user list in the User page, and search and filter functions are provided.
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/image-20240714-053822.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -42,7 +42,7 @@ Information that can be checked in the Users list is as follows. * Account Locked : Account locked due to multiple login failures
-![Description Display by Type](/administrator-manual/general/user-management/users/account-status-descriptions.png) +Description Display by Type
Description Display by Type
@@ -57,7 +57,7 @@ Add new users to your organization manually. After adding users, you can assign them to groups and policies and grant permissions.
-![Administrator > General > User Management > Users > Add User](/administrator-manual/general/user-management/users/screenshot-20240726-093805.png) +Administrator > General > User Management > Users > Add User
Administrator > General > User Management > Users > Add User
@@ -89,7 +89,7 @@ Only users with Owner role can grant Admin Role to administrators. You can grant or revoke predefined administrator roles (Admin Role) to users.
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/screenshot-20240726-100838.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -116,7 +116,7 @@ User detail information is divided into Profile, Groups, Admin Roles, Allowed Zo For descriptions of each item, please refer to the [User Profile documentation](users/user-profile).
-![Administrator > General > User Management > Users > List Details](/administrator-manual/general/user-management/users/screenshot-20240726-093748.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -138,7 +138,7 @@ In the Status dropdown within the user page, change the Status value of the user When a reason input modal is displayed, enter the reason for change and click the `OK` button to complete the change.
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/screenshot-20240726-104245.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -151,7 +151,7 @@ Click the `Deactivate` button in the user detail page to display a reason input After entering the reason and clicking the `OK` button, user deactivation is completed.
-![Administrator > General > User Management > Users > List Details ](/administrator-manual/general/user-management/users/screenshot-20240726-104608.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -174,7 +174,7 @@ In the Status dropdown within the user page, change the Status value of the user When a reason input modal is displayed, enter the reason for change and click the `OK` button to complete the change.
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/screenshot-20240726-103711.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -186,7 +186,7 @@ Click the `Reactivate` button in the detail page of the deactivated user. When a reason input modal is displayed, enter the reason for change and click the `OK` button to complete the change.
-![Administrator > General > User Management > Users > List Details ](/administrator-manual/general/user-management/users/screenshot-20240726-103241.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -205,7 +205,7 @@ Modifiable fields are activated. After completing input, click the `Save` button to complete the modification.
-![Administrator > General > User Management > Users > List Details > Edit](/administrator-manual/general/user-management/users/screenshot-20240726-094436.png) +Administrator > General > User Management > Users > List Details > Edit
Administrator > General > User Management > Users > List Details > Edit
@@ -224,7 +224,7 @@ Click the `Delete` button in the user detail page to display the Delete User con Enter "DELETE" as the confirmation phrase and click the `Delete` button to complete the deletion.
-![Administrator > General > User Management > Users > List Details > Delete User](/administrator-manual/general/user-management/users/screenshot-20240726-101758.png) +Administrator > General > User Management > Users > List Details > Delete User
Administrator > General > User Management > Users > List Details > Delete User
@@ -244,7 +244,7 @@ Administrators must issue temporary passwords in the user detail page and guide #### Issuing Temporary Passwords
-![Administrator > General > User Management > Users > List Details > Authentication](/administrator-manual/general/user-management/users/image-20241218-194814.png) +Administrator > General > User Management > Users > List Details > Authentication
Administrator > General > User Management > Users > List Details > Authentication
@@ -260,7 +260,7 @@ From QueryPie 10.2.2, when Email integration is configured, administrators can s 2. In the "Password change method" of the popup window, select "User changes own password (via email)" and click the `Confirm` button to send a password reset email to the user's email address.
-![Selecting for User to Reset Own Password via Email](/administrator-manual/general/user-management/users/image-20241218-195131.png) +Selecting for User to Reset Own Password via Email
Selecting for User to Reset Own Password via Email
@@ -271,7 +271,7 @@ The password reset link is valid for 30 minutes. If the user does not access this link for more than 30 minutes, they cannot reset their password through this link, so the administrator must perform the above procedure (User changes own password (via email)) again to send a password reset email.
-![Password Reset Email](/administrator-manual/general/user-management/users/image-20241218-224655.png) +Password Reset Email
Password Reset Email
@@ -287,7 +287,7 @@ After changing the password, click the `Change Password` button to complete the
-![Password Reset Screen](/administrator-manual/general/user-management/users/image-20241220-014612.png) +Password Reset Screen
Password Reset Screen
@@ -307,7 +307,7 @@ Click the `Reset OTP` button in the user's detail page. When a warning modal is displayed, click the `Reset` button to complete the reset.
-![Administrator > General > User Management > Users > List Details](/administrator-manual/general/user-management/users/image-20250116-131037.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
diff --git a/src/content/en/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx b/src/content/en/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx index 007456cd..376e906a 100644 --- a/src/content/en/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx +++ b/src/content/en/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx @@ -22,21 +22,21 @@ To address these risks, security-focused improvements have been introduced from 1. Access Admin > General > User Management > Users menu.
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.12.08-PM.png) + <br/>

2. Select the qp-admin account.
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.14.25-PM.png) + <br/>

3. Click the `Delete` button.
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.16.29-PM.png) + <br/>

@@ -59,7 +59,7 @@ To address these risks, security-focused improvements have been introduced from 1. When logging in with the qp-admin account, a password expiration notification screen is displayed.
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.18.40-PM.png) + <br/>

diff --git a/src/content/en/administrator-manual/general/user-management/users/user-profile.mdx b/src/content/en/administrator-manual/general/user-management/users/user-profile.mdx index 3e4ac9a4..71243c8b 100644 --- a/src/content/en/administrator-manual/general/user-management/users/user-profile.mdx +++ b/src/content/en/administrator-manual/general/user-management/users/user-profile.mdx @@ -18,7 +18,7 @@ This tab displays user attributes. For descriptions of each attribute, please refer to the **Reference: User Attribute List** section at the bottom of this page.
-![Administrator > General > User Management > Users > List Details > Profile Tab](/administrator-manual/general/user-management/users/user-profile/image-20240526-063720.png) +Administrator > General > User Management > Users > List Details > Profile Tab
Administrator > General > User Management > Users > List Details > Profile Tab
@@ -27,7 +27,7 @@ Administrator > General > User Management > Users > List Details > ### Groups
-![Administrator > General > User Management > Users > List Details > Groups Tab](/administrator-manual/general/user-management/users/user-profile/image-20240514-162350.png) +Administrator > General > User Management > Users > List Details > Groups Tab
Administrator > General > User Management > Users > List Details > Groups Tab
@@ -42,7 +42,7 @@ This tab displays the user groups to which the user belongs. ### Admin Roles
-![Administrator > General > User Management > Users > List Details > Admin Roles Tab](/administrator-manual/general/user-management/users/user-profile/image-20240514-162730.png) +Administrator > General > User Management > Users > List Details > Admin Roles Tab
Administrator > General > User Management > Users > List Details > Admin Roles Tab
@@ -61,7 +61,7 @@ This tab displays the list of QueryPie administrator privileges assigned to the You can directly assign Allowed Zones created in the Administrator > General > Company Management > Allowed Zones menu to users, or view the history of Static IPs automatically applied through the 'IP Registration Request' workflow.
-![Allowed Zones Tab](/administrator-manual/general/user-management/users/user-profile/image-20240526-064635.png) +Allowed Zones Tab
Allowed Zones Tab
@@ -79,7 +79,7 @@ When users request IP address registration through the 'IP Registration Request' These addresses registered in the `Static IP` attribute are automatically reflected in this `Allowed Zone` tab as items with `Name` set to `Static IP`, granting users access permissions from those IPs.
-![Screenshot-2025-06-26-at-6.12.22-PM.png](/administrator-manual/general/user-management/users/user-profile/Screenshot-2025-06-26-at-6.12.22-PM.png) +Screenshot-2025-06-26-at-6.12.22-PM.png
#### Deleting Static IPs Registered Through Workflow @@ -101,7 +101,7 @@ Click the `Attach Allowed Zones` button on the right side of the Allowed Zones t Select the Allowed Zone you want to assign and click the `Attach` button to complete the assignment.
-![Attach Allowed Zone Modal](/administrator-manual/general/user-management/users/user-profile/screenshot-20240730-214403.png) +Attach Allowed Zone Modal
Attach Allowed Zone Modal
@@ -113,7 +113,7 @@ Select the item you want to detach using the checkbox in the list at the bottom Click the button and then click the `Detach` button in the confirmation modal to complete the detachment.
-![Allowed Zones Detachment](/administrator-manual/general/user-management/users/user-profile/screenshot-20240730-214952.png) +Allowed Zones Detachment
Allowed Zones Detachment
diff --git a/src/content/en/administrator-manual/general/workflow-management/all-requests.mdx b/src/content/en/administrator-manual/general/workflow-management/all-requests.mdx index 7c567ea1..370cb712 100644 --- a/src/content/en/administrator-manual/general/workflow-management/all-requests.mdx +++ b/src/content/en/administrator-manual/general/workflow-management/all-requests.mdx @@ -16,7 +16,7 @@ All Requests allows you to view all request history within QueryPie and check de View the request list on the Administrator > General > Workflow Management > All Requests page.
-![Administrator > General > Workflow Management > All Requests](/administrator-manual/general/workflow-management/all-requests/image-20240714-054431.png) +Administrator > General > Workflow Management > All Requests
Administrator > General > Workflow Management > All Requests
@@ -45,7 +45,7 @@ View the progress status of the request. Hover your mouse over the box to view detailed information.
-![Administrator > General > Workflow Management > All Requests > List Detail > Current Status](/administrator-manual/general/workflow-management/all-requests/screenshot-20240725-181602.png) +Administrator > General > Workflow Management > All Requests > List Detail > Current Status
Administrator > General > Workflow Management > All Requests > List Detail > Current Status
diff --git a/src/content/en/administrator-manual/general/workflow-management/approval-rules.mdx b/src/content/en/administrator-manual/general/workflow-management/approval-rules.mdx index a4ecbd38..a44462d5 100644 --- a/src/content/en/administrator-manual/general/workflow-management/approval-rules.mdx +++ b/src/content/en/administrator-manual/general/workflow-management/approval-rules.mdx @@ -27,7 +27,7 @@ This document guides you through creating, viewing, modifying, and deleting appr View the approval rules list in the Administrator > General > Workflow Management > Approval Rules menu.
-![Administrator > General > Workflow Management > Approval Rules](/administrator-manual/general/workflow-management/approval-rules/screenshot-20240723-163151.png) +Administrator > General > Workflow Management > Approval Rules
Administrator > General > Workflow Management > Approval Rules
@@ -39,7 +39,7 @@ Administrator > General > Workflow Management > Approval Rules Click the `Add Approval Rule` button in the top right corner of the Approval Rules page to display a modal.
-![Administrator > General > Workflow Management > Approval Rules > Add Approval Rule](/administrator-manual/general/workflow-management/approval-rules/Screenshot-2025-08-26-at-4.42.57-PM.png) +Administrator > General > Workflow Management > Approval Rules > Add Approval Rule
Administrator > General > Workflow Management > Approval Rules > Add Approval Rule
@@ -118,7 +118,7 @@ In version 11.3.0, the default "Web App Just In Time Access Request" Approval Ru Click on an item in the approval rules list in Administrator > General > Workflow Management > Approval Rules to open the modal for viewing and modifying details.
-![Administrator > General > Workflow Management > Approval Rules > Update Approval Rule](/administrator-manual/general/workflow-management/approval-rules/image-20250512-121540.png) +Administrator > General > Workflow Management > Approval Rules > Update Approval Rule
Administrator > General > Workflow Management > Approval Rules > Update Approval Rule
@@ -133,7 +133,7 @@ Administrator > General > Workflow Management > Approval Rules > Upd Delete approval rules in the Administrator > General > Workflow Management > Approval Rules list.
-![Administrator > General > Workflow Management > Approval Rules (Deletion Enabled)](/administrator-manual/general/workflow-management/approval-rules/screenshot-20240725-165423.png) +Administrator > General > Workflow Management > Approval Rules (Deletion Enabled)
Administrator > General > Workflow Management > Approval Rules (Deletion Enabled)
diff --git a/src/content/en/administrator-manual/general/workflow-management/workflow-configurations.mdx b/src/content/en/administrator-manual/general/workflow-management/workflow-configurations.mdx index b4a4693e..f2f2c9ca 100644 --- a/src/content/en/administrator-manual/general/workflow-management/workflow-configurations.mdx +++ b/src/content/en/administrator-manual/general/workflow-management/workflow-configurations.mdx @@ -21,7 +21,7 @@ For Slack DM setup methods in version 10.2.5 and below, please refer to the [10. Click the `⚙️` button in the top right corner of the Approval Rules page to open the Workflow Configurations modal.
-![Administrator > General > Workflow Management > Approval Rules > Workflow Configurations](/administrator-manual/general/workflow-management/workflow-configurations/screenshot-20250310-110949.png) +Administrator > General > Workflow Management > Approval Rules > Workflow Configurations
Administrator > General > Workflow Management > Approval Rules > Workflow Configurations
@@ -63,7 +63,7 @@ When this option is activated, you can filter targets by tag in the following re * DB Access Request : You can view tags assigned to DB Connections in the list and filter to show only connections with specific tags
- ![Tag Display and Filtering in DB Access Request Form](/administrator-manual/general/workflow-management/workflow-configurations/image-20250629-180040.png) + Tag Display and Filtering in DB Access Request Form
Tag Display and Filtering in DB Access Request Form
diff --git a/src/content/en/administrator-manual/kubernetes.mdx b/src/content/en/administrator-manual/kubernetes.mdx index 10ff6d1a..3c70af64 100644 --- a/src/content/en/administrator-manual/kubernetes.mdx +++ b/src/content/en/administrator-manual/kubernetes.mdx @@ -7,7 +7,7 @@ import { Callout } from 'nextra/components' # Kubernetes
-![image-20240510-011958.png](/administrator-manual/kubernetes/image-20240510-011958.png) +image-20240510-011958.png
### Overview diff --git a/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers.mdx b/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers.mdx index b1816b55..66ea5c8f 100644 --- a/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers.mdx +++ b/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers.mdx @@ -12,7 +12,7 @@ Supports viewing, creating, modifying, and deleting Cloud Providers for Kubernet Through Cloud Providers, you can synchronize Kubernetes resources within cloud platforms and bulk register them as clusters managed by QueryPie.
-![Administrator > Kubernetes > Connection Management > Cloud Providers](/administrator-manual/kubernetes/connection-management/cloud-providers/image-20240721-053703.png) +Administrator > Kubernetes > Connection Management > Cloud Providers
Administrator > Kubernetes > Connection Management > Cloud Providers
@@ -45,7 +45,7 @@ Administrator > Kubernetes > Connection Management > Cloud Providers ### Deleting Cloud Providers
-![image-20240721-053752.png](/administrator-manual/kubernetes/connection-management/cloud-providers/image-20240721-053752.png) +image-20240721-053752.png
1. Navigate to Administrator > Kubernetes > Connection Management > Cloud Providers menu diff --git a/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx b/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx index 1678f101..cfe379e7 100644 --- a/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx +++ b/src/content/en/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx @@ -33,7 +33,7 @@ QueryPie utilizes the EKS access entry API during synchronization for AWS EKS Ku Therefore, if the cluster authentication mode is set to ConfigMap only, there may be connection difficulties, and we recommend changing the mode in the AWS console in advance for smooth synchronization.
-![AWS Console > EKS > Clusters > `{cluster}` > Access > Access configuration > Manage access](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240512-134234.png) +AWS Console > EKS > Clusters > `{cluster}` > Access > Access configuration > Manage access
AWS Console > EKS > Clusters > `{cluster}` > Access > Access configuration > Manage access
@@ -42,7 +42,7 @@ AWS Console > EKS > Clusters > `{cluster}` > Access > Access conf 1. Access AWS Console with an account that has EKS administrator privileges 2. Navigate to the **Elastic Kubernetes Service (EKS)** menu 3. Move to the region where the target EKS cluster is located - * Example: ![image-20240512-134604.png](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240512-134604.png) + * 예) image-20240512-134604.png 4. Select the target EKS cluster to navigate to the details page 5. Click the Access tab to view the Access configuration status 6. If the Authentication mode is **"ConfigMap"**, click the **Manage access** button on the right @@ -53,7 +53,7 @@ AWS Console > EKS > Clusters > `{cluster}` > Access > Access conf ### Registering AWS Integration Information in QueryPie
-![Administrator > Kubernetes > Connection Management > Cloud Providers > Create Provider](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240721-054036.png) +Administrator > Kubernetes > Connection Management > Cloud Providers > Create Provider
Administrator > Kubernetes > Connection Management > Cloud Providers > Create Provider
@@ -66,7 +66,7 @@ Administrator > Kubernetes > Connection Management > Cloud Providers &g 5. Select the region of the resources you want to synchronize from the **Region** field 6. Enter the **Credential** information required to synchronize resources
- ![image-20240721-054206.png](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240721-054206.png) + image-20240721-054206.png
1. **Default Credentials** : If the QueryPie server is installed in the same AWS account, you can assign an IAM role to the EC2 instance where QueryPie is installed to synchronize resources within the same AWS 2. **Cross Account Role** : You can create an IAM role to synchronize resources from other AWS accounts. Please create permissions for synchronization and assign policies according to the steps displayed on the screen @@ -90,7 +90,7 @@ In this case, you can register normally by selecting a different `Region`. ### Synchronizing and Managing Registered AWS Cloud Provider
-![Administrator > Kubernetes > Connection Management > Cloud Providers > List Details](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240721-054313.png) +Administrator > Kubernetes > Connection Management > Cloud Providers > List Details
Administrator > Kubernetes > Connection Management > Cloud Providers > List Details
@@ -113,13 +113,13 @@ Administrator > Kubernetes > Connection Management > Cloud Providers &g ### Dry Run/Synchronization Log Notation -| | **Occurrence Time** | **Text** | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| ✔️ | Dry Run or Synchronize synchronization start | Cluster synchronization started. | -| ✔️ | New cluster addition completed | New Cluster is added: `{Cluster Name}` (`{API URL}`). | -| ✔️ | Existing cluster information update completed | Cluster `{Cluster Name}` is updated | -| ✔️ | Existing cluster removal completed | Cluster `{Cluster Name}` is removed | -| ✔️ | Dry Run or Synchronize synchronization successfully completed | Cluster synchronization succeeded. | -| ![image-20240822-082024.png](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240822-082024.png) | Synchronization skipped when EKS cluster authentication mode does not allow EKS API. Need to change from ConfigMap mode to allow EKS API | Skipping sync. Cluster `{Cluster Name}`'s authentication mode blocks EKS access entry API. To manage access, enable EKS API access. | -| ❌ | Synchronization failed due to duplicate cluster name already confirmed | Cluster synchronization failed. The cluster name "`{Cluster Name}`" is already in use by another cluster. To synchronize it, delete the existing cluster. | -| ❌ | Dry Run or Synchronize synchronization failed | Cluster synchronization failed. + `{additional statement}` | \ No newline at end of file +| | **발생 시점** | **문구** | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| ✔️ | Dry Run 또는 Synchronize 동기화 시작 | Cluster synchronization started. | +| ✔️ | 신규 클러스터 추가 완료 | New Cluster is added: `{Cluster Name}` (`{API URL}`). | +| ✔️ | 기존 클러스터 정보 업데이트 완료 | Cluster `{Cluster Name}` is updated | +| ✔️ | 기존 클러스터 제거 완료 | Cluster `{Cluster Name}` is removed | +| ✔️ | Dry Run 또는 Synchronize 동기화 성공적으로 종료 | Cluster synchronization succeeded. | +| image-20240822-082024.png | EKS 클러스터의 인증 모드가 EKS API를 허용하지 않는 경우 동기화 스킵. ConfigMap 모드에서 EKS API를 허용하도록 변경 필요. | Skipping sync. Cluster `{Cluster Name}`'s authentication mode blocks EKS access entry API. To manage access, enable EKS API access. | +| ❌ | 이미 중복된 클러스터명이 확인되어 동기화 실패 | Cluster synchronization failed. The cluster name “`{Cluster Name}`” is already in use by another cluster. To synchronize it, delete the existing cluster. | +| ❌ | Dry Run 또는 Synchronize 동기화 실패 종료 | Cluster synchronization failed. + `{additional statement}` | diff --git a/src/content/en/administrator-manual/kubernetes/connection-management/clusters.mdx b/src/content/en/administrator-manual/kubernetes/connection-management/clusters.mdx index 3dc2d11a..3a8a1d4f 100644 --- a/src/content/en/administrator-manual/kubernetes/connection-management/clusters.mdx +++ b/src/content/en/administrator-manual/kubernetes/connection-management/clusters.mdx @@ -12,7 +12,7 @@ QueryPie supports viewing, creating, modifying, and deleting Kubernetes cluster Both Kubernetes clusters synchronized through Cloud Providers and manually registered Kubernetes clusters are managed on the same page.
-![Administrator > Kubernetes > Connection Management > Clusters](/administrator-manual/kubernetes/connection-management/clusters/image-20240721-054705.png) +Administrator > Kubernetes > Connection Management > Clusters
Administrator > Kubernetes > Connection Management > Clusters
@@ -45,7 +45,7 @@ Administrator > Kubernetes > Connection Management > Clusters ### Deleting Clusters
-![image-20240721-054752.png](/administrator-manual/kubernetes/connection-management/clusters/image-20240721-054752.png) +image-20240721-054752.png
1. Navigate to Administrator > Kubernetes > Connection Management > Clusters menu diff --git a/src/content/en/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx b/src/content/en/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx index 089fe6e3..95be1ffa 100644 --- a/src/content/en/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx +++ b/src/content/en/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx @@ -14,7 +14,7 @@ QueryPie allows you to manually register Kubernetes clusters located on-premises To manually register individual servers, you need to enter basic server information.
-![image-20240721-054859.png](/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters/image-20240721-054859.png) +image-20240721-054859.png
1. Navigate to Administrator > Kubernetes > Connection Management > Clusters menu. @@ -63,7 +63,7 @@ To manually register individual servers, you need to enter basic server informat ### Kubernetes Cluster Integration Script Usage Guide
-![image-20240511-033842.png](/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters/image-20240511-033842.png) +image-20240511-033842.png
* Administrators must be able to access the target Kubernetes cluster in advance. diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control.mdx index 7ea8d843..f6eb9ec5 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control.mdx @@ -12,7 +12,7 @@ Supports granting and revoking access permissions to Kubernetes clusters managed Access Control represents the final step in implementing and applying Kubernetes access permissions.
-![Administrator > Kubernetes > K8s Access Control > Access Control](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065226.png) +Administrator > Kubernetes > K8s Access Control > Access Control
Administrator > Kubernetes > K8s Access Control > Access Control
@@ -22,7 +22,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control ### Viewing Access Control Status
-![Administrator > Kubernetes > K8s Access Control > Access Control > List Details](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065443.png) +Administrator > Kubernetes > K8s Access Control > Access Control > List Details
Administrator > Kubernetes > K8s Access Control > Access Control > List Details
@@ -40,7 +40,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 5. Click on a row in the Access Control list to move to the detailed page for the target user/group. 1. **Roles**
- ![image-20240721-065530.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065530.png) + image-20240721-065530.png
1. This is the default tab where you can view the list of granted Roles. 2. You can search by Role name. @@ -53,7 +53,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 6. **Granted By** : Administrator name who granted the Role to the user/group 4. Click on each Role row to provide detailed information of the Role in drawer format.
- ![image-20240721-065559.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065559.png) + image-20240721-065559.png
1. Basic information is exposed at the top as follows: 1. **Name** : Role name @@ -67,7 +67,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 1. **Name** : Policy name * (Provides a link to view policy information.)
- ![image-20240721-065637.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065637.png) + image-20240721-065637.png
2. **Description** : Policy detailed description 3. **Version** : Policy version @@ -75,7 +75,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 5. **Assigned By** : Administrator name who assigned the policy 2. **Clusters**
- ![image-20240721-065710.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065710.png) + image-20240721-065710.png
1. Lists Kubernetes clusters accessible through granted Roles. 2. You can search by Cluster name and Role name. diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx index 1f214c2e..f060320d 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx @@ -13,7 +13,7 @@ Administrators can grant or revoke roles with Kubernetes API access permissions ### Granting Kubernetes Roles
-![Administrator > Kubernetes > K8s Access Control > Access Control](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-065226.png) +Administrator > Kubernetes > K8s Access Control > Access Control
Administrator > Kubernetes > K8s Access Control > Access Control
@@ -22,14 +22,14 @@ Administrator > Kubernetes > K8s Access Control > Access Control 1. Navigate to Administrator > Kubernetes > K8s Access Control > Access Control menu. 2. Select the user or user group to grant permissions to and move to the detailed page.
- ![Administrator > Kubernetes > K8s Access Control > Access Control > List Details](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-065443.png) + Administrator > Kubernetes > K8s Access Control > Access Control > List Details
Administrator > Kubernetes > K8s Access Control > Access Control > List Details
3. Click the `+ Grant Roles` button on the right of the Roles tab, check the checkbox on the left of the Role to grant, and specify the expiration date.
- ![image-20240721-070449.png](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-070449.png) + image-20240721-070449.png
1. You can search by Role name. 2. Already assigned roles have disabled checkboxes. @@ -46,14 +46,14 @@ Administrator > Kubernetes > K8s Access Control > Access Control ### Revoking Kubernetes Roles
-![image-20240721-070526.png](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-070526.png) +image-20240721-070526.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Access Control menu. 2. Select the user or user group to revoke permissions from and move to the detailed page. 3. In the Roles tab, click the `Revoke` button exposed in the column bar when checking the select all or individual selection box.
- ![image-20240721-070637.png](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-070637.png) + image-20240721-070637.png
4. When clicking the `Revoke` button in the confirmation window, the selected role permissions are revoked from the user/group and disappear from the list. 5. (Clicking the `Cancel` button only closes the confirmation window.) diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies.mdx index 23e4a3b4..19670559 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies.mdx @@ -12,7 +12,7 @@ Supports viewing, creating, modifying, and deleting access policies (Policy) for Policy is the first step in implementing and applying Kubernetes access permissions.
-![Administrator > Kubernetes > K8s Access Control > Policies](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072128.png) +Administrator > Kubernetes > K8s Access Control > Policies
Administrator > Kubernetes > K8s Access Control > Policies
@@ -22,7 +22,7 @@ Administrator > Kubernetes > K8s Access Control > Policies ### Viewing Policies
-![Administrator > Kubernetes > K8s Access Control > Policies > List Details](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072306.png) +Administrator > Kubernetes > K8s Access Control > Policies > List Details
Administrator > Kubernetes > K8s Access Control > Policies > List Details
@@ -40,13 +40,13 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 5. Click on each row to view policy detailed information. 1. **Detail**
- ![image-20240721-072345.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072345.png) + image-20240721-072345.png
1. This is the default tab where you can view the code defined by the policy. 2. When positioned in the Detail tab, there is a `Go to Editor Mode` button on the right, and clicking it switches to the Code Editor page screen. 2. **Roles**
- ![image-20240721-072412.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072412.png) + image-20240721-072412.png
1. Lists the Role list where the policy is assigned. 2. The list exposes the following information for each Role: @@ -56,7 +56,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 4. **Assigned By** : Administrator name who assigned the policy to the Role 3. Click on each row to provide detailed information about the Role in drawer format.
- ![image-20240721-072435.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072435.png) + image-20240721-072435.png
1. **Name** : Role name * Provides a link to the role detailed page. @@ -68,7 +68,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 7. **Updated By** : Last Role modifier name 3. **Versions**
- ![image-20240721-072503.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072503.png) + image-20240721-072503.png
1. Lists the history for each version of the policy. * Policy versions are updated when Code is modified and saved. @@ -79,7 +79,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 4. **Updated By** : Version modifier name 3. Click on each row to provide detailed information about the version in drawer format.
- ![image-20240721-072547.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072547.png) + image-20240721-072547.png
1. **(Title)** : Policy name 2. **Version** : Policy version @@ -92,7 +92,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Creating Policies
-![image-20240721-072621.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072621.png) +image-20240721-072621.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Policies menu. @@ -108,7 +108,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Modifying Policies
-![image-20240721-072705.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072705.png) +image-20240721-072705.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Policies menu. @@ -122,7 +122,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Duplicating Policies
-![image-20240721-072804.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072804.png) +image-20240721-072804.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Policies menu. @@ -137,7 +137,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Deleting Policies
-![image-20240721-072845.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072845.png) +image-20240721-072845.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Policies menu. diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx index 937dd7d4..e44d1bf2 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx @@ -22,7 +22,7 @@ Therefore, unless you have a specific mission to manage Kubernetes API Groups, i ### Resources Configuration Guide
-![3rd Party Client Tool - Lens screen](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide/screenshot-lens-resources-events.png) +3rd Party Client Tool - Lens screen
3rd Party Client Tool - Lens screen
diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx index 2e26fe36..8f1493b2 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx @@ -17,7 +17,7 @@ A code support modal for each field is provided on the right side of the code ed The modal serves to help with code editing, and content inserted by the entire modal can be removed from the code editor.
-![Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073114.png) +Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
@@ -25,14 +25,14 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 1. **Add Resources** modal
- ![image-20240721-073346.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073346.png) + image-20240721-073346.png
1. Works the same in both Spec: Allow and Spec: Deny. 2. You can search resources by cluster name. 3. Click the `Add` button to insert the checked resources into the code. 2. **Set Subjects** modal
- ![image-20240721-073434.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073434.png) + image-20240721-073434.png
1. Works only in Spec: Allow. 2. **Kubernetes Groups** : (Required) Specifies the Kubernetes group that QueryPie Proxy will impersonate to perform API calls through this field. @@ -43,7 +43,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 4. The modal displays existing information based on the content in the editor, and when you press the `Set` button, it overwrites the changes in the editor. 3. **Add Actions** modal
- ![image-20240721-073515.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073515.png) + image-20240721-073515.png
1. Works the same in both Spec: Allow and Spec: Deny. 2. **API Groups** : Provides "*" by default; administrators can modify and enter multiple values with ','. @@ -68,7 +68,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 8. In terms of code, it corresponds to the append part, so new additions are possible without initializing previously added actions. 4. **Set Conditions** modal
- ![image-20240721-073628.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073628.png) + image-20240721-073628.png
1. All items are optional. 2. The modal displays existing information based on the content in the editor, and when you press the `Set` button, it overwrites the changes in the editor. diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx index 57390489..3093b47e 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx @@ -14,7 +14,7 @@ You can not only set cluster resources and API scope to allow access, but also a ### Editing Policy Code
-![Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode](/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies/image-20240721-073114.png) +Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles.mdx index 0514d8e2..b75e5d8f 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles.mdx @@ -12,7 +12,7 @@ Supports viewing, creating, modifying, and deleting roles (Role) according to ac Role is the step after Policy for implementing and applying Kubernetes access permissions, meaning a collection of Policies and permissions that serve as a link between users/groups and policies.
-![Administrator > Kubernetes > K8s Access Control > Roles](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-070743.png) +Administrator > Kubernetes > K8s Access Control > Roles
Administrator > Kubernetes > K8s Access Control > Roles
@@ -22,7 +22,7 @@ Administrator > Kubernetes > K8s Access Control > Roles ### Viewing Roles
-![Administrator > Kubernetes > K8s Access Control > Roles > List Details](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-070912.png) +Administrator > Kubernetes > K8s Access Control > Roles > List Details
Administrator > Kubernetes > K8s Access Control > Roles > List Details
@@ -41,7 +41,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 5. Click on each row to view role detailed information. 1. **Policies**
- ![image-20240721-070945.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-070945.png) + image-20240721-070945.png
1. This is the default tab where you can view the list of assigned policies. 2. The table list exposes the following information for each policy: @@ -52,7 +52,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 5. **Assigned By** : Administrator name who assigned the policy 3. Click on each policy row to provide detailed information about the policy in drawer format.
- ![image-20240721-071031.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071031.png) + image-20240721-071031.png
1. Basic information is exposed at the top as follows: 1. **Name** : Policy name @@ -64,7 +64,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 2. The policy is exposed as code at the bottom. 2. **Users/Groups**
- ![image-20240721-071134.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071134.png) + image-20240721-071134.png
1. Lists the user/group list where the Role is granted. 2. You can search by user/group name. @@ -76,7 +76,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 5. **Granted At** : Date and time when the Role was granted to the user/group 3. **Clusters**
- ![image-20240721-071233.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071233.png) + image-20240721-071233.png
1. Lists the Kubernetes cluster list accessible through the Role. 2. You can search by cluster name. @@ -93,7 +93,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Creating Roles
-![image-20240721-071306.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071306.png) +image-20240721-071306.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Roles menu. @@ -109,7 +109,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Modifying Roles
-![image-20240721-071337.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071337.png) +image-20240721-071337.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Roles menu. @@ -123,7 +123,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Deleting Roles
-![image-20240721-071429.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071429.png) +image-20240721-071429.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Roles menu. diff --git a/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx b/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx index 7cebc711..0d7bf670 100644 --- a/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx +++ b/src/content/en/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx @@ -16,7 +16,7 @@ Roles are used to define multiple policies as a single role. ### Assigning Role Policies
-![Administrator > Kubernetes > K8s Access Control > Roles > List Details](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071540.png) +Administrator > Kubernetes > K8s Access Control > Roles > List Details
Administrator > Kubernetes > K8s Access Control > Roles > List Details
@@ -27,7 +27,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 3. Click the `+ Assign Policies` button on the right of the Policies tab. 4. Review the policies to assign, then check the checkbox on the left.
- ![image-20240721-071758.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071758.png) + image-20240721-071758.png
1. You can search by policy name. 2. Already assigned policies have disabled checkboxes. @@ -35,7 +35,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai * **Name** : Policy name * Provides a modal link to view policy information.
- ![image-20240721-071822.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071822.png) + image-20240721-071822.png
5. Press the `Assign` button to assign the checked target policies. 6. (Pressing the `Cancel` button closes the modal without changes.) @@ -44,14 +44,14 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Unassigning Role Policies
-![image-20240721-071910.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071910.png) +image-20240721-071910.png
1. Navigate to Administrator > Kubernetes > K8s Access Control > Roles menu. 2. Click on the target Role row from the Roles list to move to the detailed page. 3. In the Policies tab, click the `Unassign` button exposed in the column bar when checking the select all or individual selection box.
- ![image-20240721-071940.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071940.png) + image-20240721-071940.png
4. When clicking the `Unassign` button in the confirmation window, the selected items are unassigned and disappear from the list. 5. (Clicking the `Cancel` button only closes the confirmation window.) diff --git a/src/content/en/administrator-manual/kubernetes/kac-general-configurations.mdx b/src/content/en/administrator-manual/kubernetes/kac-general-configurations.mdx index 67ea3ca6..fbc99709 100644 --- a/src/content/en/administrator-manual/kubernetes/kac-general-configurations.mdx +++ b/src/content/en/administrator-manual/kubernetes/kac-general-configurations.mdx @@ -17,7 +17,7 @@ Starting from 11.4.0, the Maximum Access Duration option has been added to speci Provides settings for security in container-based environments, such as Kubernetes cluster access control, permission management, and session policies.
-![Kubernetes Configurations options](/administrator-manual/kubernetes/kac-general-configurations/image-20251107-090909.png) +Kubernetes Configurations options
Kubernetes Configurations options
diff --git a/src/content/en/administrator-manual/servers.mdx b/src/content/en/administrator-manual/servers.mdx index 3838d1b4..37f1ead6 100644 --- a/src/content/en/administrator-manual/servers.mdx +++ b/src/content/en/administrator-manual/servers.mdx @@ -7,7 +7,7 @@ import { Callout } from 'nextra/components' # Servers
-![screenshot-20240523-195046.png](/administrator-manual/servers/screenshot-20240523-195046.png) +screenshot-20240523-195046.png
### Overview diff --git a/src/content/en/administrator-manual/servers/connection-management/cloud-providers.mdx b/src/content/en/administrator-manual/servers/connection-management/cloud-providers.mdx index 89873f16..beb432eb 100644 --- a/src/content/en/administrator-manual/servers/connection-management/cloud-providers.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/cloud-providers.mdx @@ -12,7 +12,7 @@ QueryPie supports integration with Cloud Providers for server registration and m You can synchronize resources within Cloud Providers, register them as servers managed by QueryPie, and grant access permissions and set policies for users and groups on the synchronized servers.
-![Administrator > Servers > Connection Management > Cloud Providers](/administrator-manual/servers/connection-management/cloud-providers/image-20240902-044659.png) +Administrator > Servers > Connection Management > Cloud Providers
Administrator > Servers > Connection Management > Cloud Providers
@@ -46,7 +46,7 @@ Administrator > Servers > Connection Management > Cloud Providers ### Deleting Cloud Providers
-![image-20240902-044732.png](/administrator-manual/servers/connection-management/cloud-providers/image-20240902-044732.png) +image-20240902-044732.png
1. Navigate to Administrator > Servers > Connection Management > Cloud Providers menu. diff --git a/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx b/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx index 9024a3de..ab7e86ba 100644 --- a/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx @@ -16,7 +16,7 @@ Additionally, you can automatically add server groups to servers that have been ### Registering AWS Integration Information in QueryPie
-![Administrator > Servers > Connection Management > Cloud Providers > Create Provider](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20241220-095625.png) +Administrator > Servers > Connection Management > Cloud Providers > Create Provider
Administrator > Servers > Connection Management > Cloud Providers > Create Provider
@@ -53,7 +53,7 @@ In this case, you must select a different `Region` to register. ### Setting Authentication Methods by Credential Type
-![Credential Type](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20240902-044927.png) +Credential Type
Credential Type
@@ -68,7 +68,7 @@ Credential Type **Save Credential for Synchronization Option**
-![Save Credential for Synchronization](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20241220-095857.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -83,7 +83,7 @@ Save Credential for Synchronization ### Synchronizing and Managing Registered AWS Cloud Provider
-![Administrator > Servers > Connection Management > Cloud Providers > List Details](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20241220-100236.png) +Administrator > Servers > Connection Management > Cloud Providers > List Details
Administrator > Servers > Connection Management > Cloud Providers > List Details
diff --git a/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx b/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx index 25b3f571..891956f2 100644 --- a/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx @@ -15,7 +15,7 @@ You can synchronize resources within Azure, register them as servers managed by ### Registering Azure Integration Information in QueryPie
-![Administrator > Servers > Connection Management > Cloud Providers > Create Provider](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure/image-20241220-101742.png) +Administrator > Servers > Connection Management > Cloud Providers > Create Provider
Administrator > Servers > Connection Management > Cloud Providers > Create Provider
@@ -48,7 +48,7 @@ Administrator > Servers > Connection Management > Cloud Providers > **Save Credential for Synchronization Option**
-![Save Credential for Synchronization](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure/image-20241220-091144.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -62,7 +62,7 @@ Save Credential for Synchronization ### Synchronizing and Managing Registered Azure Cloud Provider
-![Administrator > Servers > Connection Management > Cloud Providers > List Details](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure/image-20241220-104437.png) +Administrator > Servers > Connection Management > Cloud Providers > List Details
Administrator > Servers > Connection Management > Cloud Providers > List Details
diff --git a/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx b/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx index 7d3c13e1..bf73634e 100644 --- a/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx @@ -15,7 +15,7 @@ You can synchronize resources within GCP, register them as servers managed by Qu ### Registering GCP Integration Information in QueryPie
-![Administrator > Servers > Connection Management > Cloud Providers > Create Provider](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp/image-20241220-120114.png) +Administrator > Servers > Connection Management > Cloud Providers > Create Provider
Administrator > Servers > Connection Management > Cloud Providers > Create Provider
@@ -47,7 +47,7 @@ Administrator > Servers > Connection Management > Cloud Providers > **Save Credential for Synchronization Option**
-![Save Credential for Synchronization](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp/image-20241220-094727.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -61,7 +61,7 @@ Save Credential for Synchronization ### Synchronizing and Managing Registered GCP Cloud Provider
-![Administrator > Servers > Connection Management > Cloud Providers > List Details](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp/image-20241222-132041.png) +Administrator > Servers > Connection Management > Cloud Providers > List Details
Administrator > Servers > Connection Management > Cloud Providers > List Details
diff --git a/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations.mdx b/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations.mdx index ddac706c..cee3510c 100644 --- a/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations.mdx @@ -15,7 +15,7 @@ This allows you to control unnecessary user access to Jump Hosts. ### Viewing ProxyJump
-![Administrator > Servers > Connection Management > ProxyJump Configurations](/administrator-manual/servers/connection-management/proxyjump-configurations/image-20240829-012626.png) +Administrator > Servers > Connection Management > ProxyJump Configurations
Administrator > Servers > Connection Management > ProxyJump Configurations
@@ -42,7 +42,7 @@ Administrator > Servers > Connection Management > ProxyJump Configurati ### Deleting ProxyJump
-![image-20240909-083933.png](/administrator-manual/servers/connection-management/proxyjump-configurations/image-20240909-083933.png) +image-20240909-083933.png
1. Navigate to Administrator > Servers > Connection Management > ProxyJump Configurations menu. diff --git a/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx b/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx index f6d72df0..dc998c76 100644 --- a/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx @@ -16,7 +16,7 @@ Proxyjump for Windows Servers is also supported. ### Creating ProxyJump
-![Administrator > Servers > Connection Management > ProxyJump Configurations > Create ProxyJump](/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump/image-20250116-115457.png) +Administrator > Servers > Connection Management > ProxyJump Configurations > Create ProxyJump
Administrator > Servers > Connection Management > ProxyJump Configurations > Create ProxyJump
diff --git a/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx b/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx index 01e23987..00983a54 100644 --- a/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx @@ -21,7 +21,7 @@ You can also check RDP sessions in real-time and force terminate connected RDP s
-![Administrator > Servers > Connection Management > Server Agents for RDP](/administrator-manual/servers/connection-management/server-agents-for-rdp/image-20250707-011843.png) +Administrator > Servers > Connection Management > Server Agents for RDP
Administrator > Servers > Connection Management > Server Agents for RDP
@@ -68,7 +68,7 @@ However, if communication from Server Agent to QueryPie is possible but communic In this case, it can be resolved as follows.
-![image-20240731-024502.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/image-20240731-024502.png) +image-20240731-024502.png
1. Navigate to Administrator > Servers > Connection Management > Server Agents for RDP menu. @@ -89,7 +89,7 @@ Updates proceed to agent versions compatible with the currently used QueryPie ve ### Deleting Server Agents
-![image-20240728-154821.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/image-20240728-154821.png) +image-20240728-154821.png
1. Navigate to Administrator > Servers > Connection Management > Server Agents for RDP menu. diff --git a/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx b/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx index 41f10c5d..0c5a102b 100644 --- a/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx @@ -15,7 +15,7 @@ After installing QueryPie Server Agent, Windows Servers are automatically added ### Installing Server Agent
-![image-20240728-163032.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent/image-20240728-163032.png) +image-20240728-163032.png
* Access the Server Agent download page. @@ -26,7 +26,7 @@ In 11.3.0, administrators can also download server agents through the UI (the `D You can still download using the existing download link page. (Use this when non-QueryPie users need to download agents externally)
-![RDP Server Agent Download Button Provided](/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent/image-20251010-085601.png) +RDP Server Agent Download Button Provided
RDP Server Agent Download Button Provided
@@ -89,7 +89,7 @@ After moving to the Server Agent installation file location in CMD, execute the ### Removing Server Agent
-![image-20240829-010643.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent/image-20240829-010643.png) +image-20240829-010643.png
1. Access the Administrator > Servers > Connection Management > Server Agents for RDP page. diff --git a/src/content/en/administrator-manual/servers/connection-management/server-groups.mdx b/src/content/en/administrator-manual/servers/connection-management/server-groups.mdx index ab6a9f4c..4609c876 100644 --- a/src/content/en/administrator-manual/servers/connection-management/server-groups.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/server-groups.mdx @@ -10,7 +10,7 @@ QueryPie can set policies and grant access permissions by Server Group unit. You can also select servers in bulk through server tags, or have servers synchronized later automatically selected in server groups.
-![Administrator > Servers > Connection Management > Server Groups](/administrator-manual/servers/connection-management/server-groups/image-20240902-045633.png) +Administrator > Servers > Connection Management > Server Groups
Administrator > Servers > Connection Management > Server Groups
@@ -40,7 +40,7 @@ Administrator > Servers > Connection Management > Server Groups ### Deleting Server Groups
-![image-20240728-151520.png](/administrator-manual/servers/connection-management/server-groups/image-20240728-151520.png) +image-20240728-151520.png
1. Navigate to Administrator > Servers > Connection Management > Server Groups menu. diff --git a/src/content/en/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx b/src/content/en/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx index 60d75c03..5fbbfee9 100644 --- a/src/content/en/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx @@ -21,7 +21,7 @@ We recommend registering each resource required for server group registration in ### Creating Server Groups
-![Administrator > Servers > Connection Management > Server Groups > Create Server Group](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20250123-113012.png) +Administrator > Servers > Connection Management > Server Groups > Create Server Group
Administrator > Servers > Connection Management > Server Groups > Create Server Group
@@ -50,7 +50,7 @@ Some items can be modified after creation. #### 1. Entering Basic Information and Adding Servers by Tag
-![image-20240902-045749.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20240902-045749.png) +image-20240902-045749.png
* Name : Enter the name of the server group. @@ -60,7 +60,7 @@ Some items can be modified after creation. #### 2. Manually Adding Servers
-![image-20241028-003400.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20241028-003400.png) +image-20241028-003400.png
* In Servers, you can check servers that belong to the server group or manually add servers to the server group. @@ -72,7 +72,7 @@ Some items can be modified after creation. In 11.3.0, you can now filter targets using tags in the popup for adding servers to Server groups.
-![Example of filtering targets to add to Server Group using tags](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20251010-084037.png) +Example of filtering targets to add to Server Group using tags
Example of filtering targets to add to Server Group using tags
@@ -90,7 +90,7 @@ Test Connection can only be used after saving the Server Group. #### 3. Registering Accounts
-![Screenshot-2025-07-27-at-10.33.48-PM.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/Screenshot-2025-07-27-at-10.33.48-PM.png) +Screenshot-2025-07-27-at-10.33.48-PM.png
1. Register and manage Accounts required to access the connection. There are two ways to register Accounts. @@ -99,11 +99,11 @@ Test Connection can only be used after saving the Server Group. 2. Or you can manually add Accounts using the `Add Account` function. 1. When clicking the `Add Account` button, a modal window for account settings is displayed. Items to be entered differ for each selected Category.
- ![Screenshot-2025-07-27-at-10.37.35-PM.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/Screenshot-2025-07-27-at-10.37.35-PM.png) + Screenshot-2025-07-27-at-10.37.35-PM.png
2. Accounts designated as Provisioning accounts display a key icon next to the Account.
- ![Screenshot-2025-07-27-at-10.35.23-PM.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/Screenshot-2025-07-27-at-10.35.23-PM.png) + Screenshot-2025-07-27-at-10.35.23-PM.png
3. You can set accounts by category. 1. Category : You must first select a Category that defines the authentication method and type of the account. The setting items displayed below change dynamically according to the selected Category. @@ -200,7 +200,7 @@ Therefore, when accessing macOS servers through QueryPie, users must directly en #### 4. Registering Server Group Owner
-![image-20250512-105127.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20250512-105127.png) +image-20250512-105127.png
You can register server group owners to designate them as approvers in Workflow. @@ -214,7 +214,7 @@ You can register server group owners to designate them as approvers in Workflow. #### 5. Registering Server Group Member
-![image-20250512-105142.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20250512-105142.png) +image-20250512-105142.png
You can register server group members to specify Server Groups displayed in user-specific Workflow. diff --git a/src/content/en/administrator-manual/servers/connection-management/servers.mdx b/src/content/en/administrator-manual/servers/connection-management/servers.mdx index 3fc7b743..5fac9bdf 100644 --- a/src/content/en/administrator-manual/servers/connection-management/servers.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/servers.mdx @@ -12,7 +12,7 @@ QueryPie supports viewing, creating, modifying, and deleting Server assets. Servers synchronized through Cloud Providers, APIs, or manually registered servers are all managed on the same page.
-![Administrator > Servers > Connection Management > Servers](/administrator-manual/servers/connection-management/servers/image-20240902-045519.png) +Administrator > Servers > Connection Management > Servers
Administrator > Servers > Connection Management > Servers
@@ -46,7 +46,7 @@ Administrator > Servers > Connection Management > Servers ### Deleting Servers
-![image-20240723-162214.png](/administrator-manual/servers/connection-management/servers/image-20240723-162214.png) +image-20240723-162214.png
1. Navigate to Administrator > Servers > Connection Management > Servers menu. diff --git a/src/content/en/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx b/src/content/en/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx index 151f2a6e..e69dcd04 100644 --- a/src/content/en/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx +++ b/src/content/en/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx @@ -16,7 +16,7 @@ However, Windows servers cannot be manually registered and can only be automatic To manually register individual servers, you need to enter basic server information.
-![Administrator > Servers > Connection Management > Servers > Create Server](/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers/image-20240828-154238.png) +Administrator > Servers > Connection Management > Servers > Create Server
Administrator > Servers > Connection Management > Servers > Create Server
@@ -25,7 +25,7 @@ Administrator > Servers > Connection Management > Servers > Create S #### 1. Entering Information
-![image-20240828-154305.png](/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers/image-20240828-154305.png) +image-20240828-154305.png
1. Navigate to Administrator > Servers > Connection Management > Servers menu. @@ -44,7 +44,7 @@ Administrator > Servers > Connection Management > Servers > Create S #### 2. Entering Tags (Optional)
-![image-20240723-163036.png](/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers/image-20240723-163036.png) +image-20240723-163036.png
You can manually enter Tags for individual servers if necessary. diff --git a/src/content/en/administrator-manual/servers/sac-general-configurations.mdx b/src/content/en/administrator-manual/servers/sac-general-configurations.mdx index 565d0229..1b6c4623 100644 --- a/src/content/en/administrator-manual/servers/sac-general-configurations.mdx +++ b/src/content/en/administrator-manual/servers/sac-general-configurations.mdx @@ -26,7 +26,7 @@ Manage security settings applied to server access control. Manage basic security settings.
-![image-20251218-084954.png](/administrator-manual/servers/sac-general-configurations/image-20251218-084954.png) +image-20251218-084954.png
@@ -68,7 +68,7 @@ Manage basic security settings. * Applied with priority over Roles or Direct Permissions granted to Users/Groups * When the `Add Configuration` button is clicked, a modal is created and the following information is entered to click the `Add` button (not reflected until the `Save Changes` button in the top right is clicked)
- ![image-20240829-095257.png](/administrator-manual/servers/sac-general-configurations/image-20240829-095257.png) + image-20240829-095257.png
* **Server Tag Key** : Enter the server tag key, only one can be applied at a time (required when used) * **Server Tag Value** : Enter the server tag value, only one can be applied at a time (required when used) @@ -121,7 +121,7 @@ For more details, please refer to [Requesting Server Access Request](../../user-
-![Screenshot-2025-07-22-at-3.09.36-PM.png](/administrator-manual/servers/sac-general-configurations/Screenshot-2025-07-22-at-3.09.36-PM.png) +Screenshot-2025-07-22-at-3.09.36-PM.png
* Maximum Access Duration : Set the maximum usage period for server access permissions @@ -158,7 +158,7 @@ For more details, please refer to [Requesting Server Privilege Request](../../us
-![Screenshot-2025-07-22-at-3.15.31-PM.png](/administrator-manual/servers/sac-general-configurations/Screenshot-2025-07-22-at-3.15.31-PM.png) +Screenshot-2025-07-22-at-3.15.31-PM.png
* **Maximum Access Duration** : Set the maximum duration for privilege usage diff --git a/src/content/en/administrator-manual/servers/server-access-control/access-control.mdx b/src/content/en/administrator-manual/servers/server-access-control/access-control.mdx index c8878631..d384edf8 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/access-control.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/access-control.mdx @@ -10,7 +10,7 @@ Supports granting and revoking management of access permissions to servers manag Access Control represents the final step for granting and applying server access permissions.
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/servers/server-access-control/access-control/image-20240902-051205.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
diff --git a/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx b/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx index 714f80eb..3be148de 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx @@ -17,7 +17,7 @@ Once granted, Permissions cannot be modified and can only be deleted. #### 1. Select the target to grant permissions to.
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/image-20240828-015212.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
@@ -29,7 +29,7 @@ Administrator > Servers > Server Access Control > Access Control #### 2.**[Step 1]**: Select the account of the server or server group to grant permissions to.
-![Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 1](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/image-20240828-015324.png) +Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 1
Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 1
@@ -49,7 +49,7 @@ If more than 1000 servers are registered in a single server group, add servers t #### 3.**[Step 2]**: Set access policies for the selected servers.
-![Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 2](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/Screenshot-2025-07-27-at-5.28.54-PM.png) +Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 2
Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 2
@@ -89,7 +89,7 @@ Administrator > Servers > Server Access Control > Access Control > D ### Revoking Access Control Permissions
-![Administrator > Servers > Server Access Control > Access Control > Servers](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/image-20240421-025726.png) +Administrator > Servers > Server Access Control > Access Control > Servers
Administrator > Servers > Server Access Control > Access Control > Servers
diff --git a/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx b/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx index dd525d6b..a721515d 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx @@ -16,7 +16,7 @@ Administrators can grant or revoke roles (Role) with server access permissions t #### 1. Select the target to grant permissions to.
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-051928.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
@@ -28,7 +28,7 @@ Administrator > Servers > Server Access Control > Access Control #### 2. Select the Role to grant permissions to.
-![Administrator > Servers > Server Access Control > Access Control > List Details > Roles tab](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-051957.png) +Administrator > Servers > Server Access Control > Access Control > List Details > Roles tab
Administrator > Servers > Server Access Control > Access Control > List Details > Roles tab
@@ -37,7 +37,7 @@ Administrator > Servers > Server Access Control > Access Control > L 1. Select the Roles tab in the left center of the screen. 2. Click the `+ Grant Roles` button in the right center.
- ![image-20240902-052029.png](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-052029.png) + image-20240902-052029.png
3. Check the checkbox on the left of the Role to grant. 4. Enter the Expiration Date. The default value is 1 year. @@ -47,7 +47,7 @@ Administrator > Servers > Server Access Control > Access Control > L ### Revoking Roles
-![Server Settings > Server Access Control > Access Control > List Details > Roles tab](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-052047.png) +Server Settings > Server Access Control > Access Control > List Details > Roles tab
Server Settings > Server Access Control > Access Control > List Details > Roles tab
diff --git a/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx b/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx index fabc42c7..e5482c80 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx @@ -15,7 +15,7 @@ When granting Server Privilege again to a target that already has Server Privile ### Granting Server Privilege
-![Administrator > Servers > Server Access Control > Access Control > User/Group > Servers > Server Details](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/image-20250307-121546.png) +Administrator > Servers > Server Access Control > Access Control > User/Group > Servers > Server Details
Administrator > Servers > Server Access Control > Access Control > User/Group > Servers > Server Details
@@ -37,19 +37,19 @@ Administrator > Servers > Server Access Control > Access Control > U 6. The modal items vary depending on the server's OS and Require Privilege option status. 1. When the server's OS is Linux and the Require Privilege option is enabled
- ![Screenshot-2025-07-02-at-5.14.50-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-02-at-5.14.50-PM.png) + Screenshot-2025-07-02-at-5.14.50-PM.png
2. When the server's OS is Linux and the Require Privilege option is disabled
- ![Screenshot-2025-07-01-at-5.58.34-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-01-at-5.58.34-PM.png) + Screenshot-2025-07-01-at-5.58.34-PM.png
3. When the server's OS is not Linux and the Require Privilege option is enabled
- ![Screenshot-2025-07-01-at-6.02.23-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-01-at-6.02.23-PM.png) + Screenshot-2025-07-01-at-6.02.23-PM.png
4. When the server's OS is not Linux and the Require Privilege option is disabled
- ![Screenshot-2025-07-02-at-5.10.49-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-02-at-5.10.49-PM.png) + Screenshot-2025-07-02-at-5.10.49-PM.png
diff --git a/src/content/en/administrator-manual/servers/server-access-control/blocked-accounts.mdx b/src/content/en/administrator-manual/servers/server-access-control/blocked-accounts.mdx index 8ed63d0a..aede1398 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/blocked-accounts.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/blocked-accounts.mdx @@ -14,7 +14,7 @@ We provide administrators with a menu to manage deactivated server accounts, whe ### Activating Server Accounts
-![Administrator > Servers > Server Access Control > Blocked Accounts](/administrator-manual/servers/server-access-control/blocked-accounts/image-20240902-053139.png) +Administrator > Servers > Server Access Control > Blocked Accounts
Administrator > Servers > Server Access Control > Blocked Accounts
diff --git a/src/content/en/administrator-manual/servers/server-access-control/command-templates.mdx b/src/content/en/administrator-manual/servers/server-access-control/command-templates.mdx index 89d7edfc..df550c68 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/command-templates.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/command-templates.mdx @@ -14,7 +14,7 @@ Command blocking is based on strings, and command blocking through regular expre Additionally, you can standardize the list of commands that users can select in the server privilege request process to improve management efficiency.
-![Administrator > Servers > Server Access Control > Command Templates](/administrator-manual/servers/server-access-control/command-templates/image-20240902-053009.png) +Administrator > Servers > Server Access Control > Command Templates
Administrator > Servers > Server Access Control > Command Templates
@@ -26,7 +26,7 @@ Server access policies can be set in the Policies menu. For setting methods, refer to the **commandsRef** section in [Setting Server Access Policies](policies/setting-server-access-policy).
-![Administrator > Servers > Server Access Control > Command Templates > Create Command Template](/administrator-manual/servers/server-access-control/command-templates/Screenshot-2025-07-22-at-3.23.24-PM.png) +Administrator > Servers > Server Access Control > Command Templates > Create Command Template
Administrator > Servers > Server Access Control > Command Templates > Create Command Template
diff --git a/src/content/en/administrator-manual/servers/server-access-control/policies.mdx b/src/content/en/administrator-manual/servers/server-access-control/policies.mdx index d4070b9f..821738ff 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/policies.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/policies.mdx @@ -12,7 +12,7 @@ QueryPie server access policies (Policy) are functions for managing and applying You can set detailed policies such as when to allow access and which commands to prohibit for each server or server group, so that users or groups can access only the minimum necessary servers according to their business purposes.
-![Administrator > Servers > Server Access Control > Policies](/administrator-manual/servers/server-access-control/policies/image-20240902-052616.png) +Administrator > Servers > Server Access Control > Policies
Administrator > Servers > Server Access Control > Policies
@@ -30,7 +30,7 @@ Administrator > Servers > Server Access Control > Policies ### Viewing Policies
-![Administrator > Servers > Server Access Control > Policies > List Details](/administrator-manual/servers/server-access-control/policies/image-20240902-052643.png) +Administrator > Servers > Server Access Control > Policies > List Details
Administrator > Servers > Server Access Control > Policies > List Details
@@ -42,7 +42,7 @@ Administrator > Servers > Server Access Control > Policies > List De #### Detail Tab
-![screenshot-20240808-171818.png](/administrator-manual/servers/server-access-control/policies/screenshot-20240808-171818.png) +screenshot-20240808-171818.png
1. This is the default tab where you can view the code defined by the policy. @@ -52,7 +52,7 @@ Administrator > Servers > Server Access Control > Policies > List De #### Roles Tab
-![image-20240723-115930.png](/administrator-manual/servers/server-access-control/policies/image-20240723-115930.png) +image-20240723-115930.png
1. Lists the Role list where this policy is assigned. @@ -66,7 +66,7 @@ Administrator > Servers > Server Access Control > Policies > List De #### Versions Tab
-![image-20240723-120008.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120008.png) +image-20240723-120008.png
1. Lists the history for each version of this policy. @@ -85,14 +85,14 @@ Administrator > Servers > Server Access Control > Policies > List De 6. The **policy code snapshot** at that time is displayed at the bottom.
-![image-20240723-120033.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120033.png) +image-20240723-120033.png
### Creating Policies
-![image-20240723-120134.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120134.png) +image-20240723-120134.png
1. Navigate to Administrator > Servers > Server Access Control > Policies menu. @@ -106,7 +106,7 @@ Administrator > Servers > Server Access Control > Policies > List De ### Modifying Policies
-![image-20240723-120317.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120317.png) +image-20240723-120317.png
1. Navigate to Administrator > Servers > Server Access Control > Policies menu. @@ -120,7 +120,7 @@ Administrator > Servers > Server Access Control > Policies > List De ### Deleting Policies
-![image-20240723-120357.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120357.png) +image-20240723-120357.png
1. Navigate to Administrator > Servers > Server Access Control > Policies menu. diff --git a/src/content/en/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx b/src/content/en/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx index 601845b7..88ef1f6b 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx @@ -35,7 +35,7 @@ In addition, you can set the number of allowed sessions per user. ### Editing Policy Code
-![Administrator > Servers > Server Access Control > Policies > List Details > Go to Editor Mode](/administrator-manual/servers/server-access-control/policies/setting-server-access-policy/Screenshot-2025-07-27-at-5.40.59-PM.png) +Administrator > Servers > Server Access Control > Policies > List Details > Go to Editor Mode
Administrator > Servers > Server Access Control > Policies > List Details > Go to Editor Mode
diff --git a/src/content/en/administrator-manual/servers/server-access-control/roles.mdx b/src/content/en/administrator-manual/servers/server-access-control/roles.mdx index 8f9589f1..99e9d122 100644 --- a/src/content/en/administrator-manual/servers/server-access-control/roles.mdx +++ b/src/content/en/administrator-manual/servers/server-access-control/roles.mdx @@ -13,7 +13,7 @@ You can assign set Roles to users or user groups. Roles are used to define multiple policies as a single role.
-![Administrator > Servers > Server Access Control > Roles](/administrator-manual/servers/server-access-control/roles/image-20240902-052135.png) +Administrator > Servers > Server Access Control > Roles
Administrator > Servers > Server Access Control > Roles
@@ -34,7 +34,7 @@ Administrator > Servers > Server Access Control > Roles ### Viewing Roles
-![Administrator > Servers > Server Access Control > Roles > List Details](/administrator-manual/servers/server-access-control/roles/image-20240902-052205.png) +Administrator > Servers > Server Access Control > Roles > List Details
Administrator > Servers > Server Access Control > Roles > List Details
@@ -52,7 +52,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai 5. **Assigned By** : Administrator name who assigned this policy 3. Clicking each policy row provides detailed information about that policy in drawer format.
- ![image-20240902-052235.png](/administrator-manual/servers/server-access-control/roles/image-20240902-052235.png) + image-20240902-052235.png
1. Basic information is displayed at the top as follows: 1. **Name** : Policy name @@ -64,7 +64,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai 2. The policy is displayed as code at the bottom. 2. **Users/Groups**
- ![image-20240902-052352.png](/administrator-manual/servers/server-access-control/roles/image-20240902-052352.png) + image-20240902-052352.png
1. Lists the user/group list where this Role is assigned. 2. You can search by user/group name. @@ -76,7 +76,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai 5. **Granted At** : Date and time when this Role was assigned to the user/group 3. **Servers**
- ![image-20240902-052432.png](/administrator-manual/servers/server-access-control/roles/image-20240902-052432.png) + image-20240902-052432.png
1. Lists the server list accessible by this Role. 2. You can search by Server name. @@ -89,7 +89,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai ### Creating Roles
-![image-20240723-081606.png](/administrator-manual/servers/server-access-control/roles/image-20240723-081606.png) +image-20240723-081606.png
1. Navigate to Administrator > Servers > Server Access Control > Roles menu. @@ -103,7 +103,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai ### Modifying Roles
-![Administrator > Servers > Server Access Control > Roles > List Details](/administrator-manual/servers/server-access-control/roles/image-20240902-052459.png) +Administrator > Servers > Server Access Control > Roles > List Details
Administrator > Servers > Server Access Control > Roles > List Details
diff --git a/src/content/en/administrator-manual/servers/server-account-management/account-management.mdx b/src/content/en/administrator-manual/servers/server-account-management/account-management.mdx index 7a8a91a6..d3000acf 100644 --- a/src/content/en/administrator-manual/servers/server-account-management/account-management.mdx +++ b/src/content/en/administrator-manual/servers/server-account-management/account-management.mdx @@ -17,7 +17,7 @@ This menu is displayed only after selecting **Password Provisioning** setting to ### Viewing Accounts
-![Administrator > Servers > Server Account Management > Account Management ](/administrator-manual/servers/server-account-management/account-management/Screenshot-2025-07-27-at-6.47.45-PM.png) +Administrator > Servers > Server Account Management > Account Management
Administrator > Servers > Server Account Management > Account Management
@@ -41,7 +41,7 @@ Administrator > Servers > Server Account Management > Account Managemen ### Viewing One Time Accounts
-![Administrator > Servers > Server Account Management > Account Management > One Time Accounts tab](/administrator-manual/servers/server-account-management/account-management/Screenshot-2025-07-27-at-6.50.29-PM.png) +Administrator > Servers > Server Account Management > Account Management > One Time Accounts tab
Administrator > Servers > Server Account Management > Account Management > One Time Accounts tab
@@ -62,7 +62,7 @@ Administrator > Servers > Server Account Management > Account Managemen ### Viewing Active Directory
-![Administrator > Servers > Server Account Management > Account Management > Active Directory tab](/administrator-manual/servers/server-account-management/account-management/Screenshot-2025-07-27-at-7.03.55-PM.png) +Administrator > Servers > Server Account Management > Account Management > Active Directory tab
Administrator > Servers > Server Account Management > Account Management > Active Directory tab
@@ -81,7 +81,7 @@ Administrator > Servers > Server Account Management > Account Managemen ### Viewing Account Detailed Information
-![image-20240831-155640.png](/administrator-manual/servers/server-account-management/account-management/image-20240831-155640.png) +image-20240831-155640.png
1. Navigate to Administrator > Servers > Server Account Management > Account Management menu diff --git a/src/content/en/administrator-manual/servers/server-account-management/password-provisioning.mdx b/src/content/en/administrator-manual/servers/server-account-management/password-provisioning.mdx index 01af1efe..9805ed48 100644 --- a/src/content/en/administrator-manual/servers/server-account-management/password-provisioning.mdx +++ b/src/content/en/administrator-manual/servers/server-account-management/password-provisioning.mdx @@ -19,7 +19,7 @@ This menu is displayed only after selecting **Password Provisioning** setting to ### Viewing Password Change Jobs
-![Administrator > Servers > Server Account Management > Password Provisioning](/administrator-manual/servers/server-account-management/password-provisioning/Screenshot-2025-07-27-at-6.31.29-PM.png) +Administrator > Servers > Server Account Management > Password Provisioning
Administrator > Servers > Server Account Management > Password Provisioning
@@ -39,7 +39,7 @@ Administrator > Servers > Server Account Management > Password Provisio ### Viewing Active Directory Password Change Jobs
-![Administrator > Servers > Server Account Management > Password Provisioning](/administrator-manual/servers/server-account-management/password-provisioning/Screenshot-2025-07-27-at-6.33.43-PM.png) +Administrator > Servers > Server Account Management > Password Provisioning
Administrator > Servers > Server Account Management > Password Provisioning
@@ -58,7 +58,7 @@ Administrator > Servers > Server Account Management > Password Provisio ### Changing Active Directory Passwords
-![Screenshot-2025-07-27-at-7.22.21-PM.png](/administrator-manual/servers/server-account-management/password-provisioning/Screenshot-2025-07-27-at-7.22.21-PM.png) +Screenshot-2025-07-27-at-7.22.21-PM.png
1. Navigate to Administrator > Servers > Server Account Management > Password Provisioning > Active Directory tab > password detailed screen. @@ -74,7 +74,7 @@ Administrator > Servers > Server Account Management > Password Provisio ### Deleting Password Change Jobs
-![image-20240831-161802.png](/administrator-manual/servers/server-account-management/password-provisioning/image-20240831-161802.png) +image-20240831-161802.png
1. Navigate to Administrator > Servers > Server Account Management > Password Provisioning menu. diff --git a/src/content/en/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx b/src/content/en/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx index 63e8d62d..69884deb 100644 --- a/src/content/en/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx +++ b/src/content/en/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx @@ -20,7 +20,7 @@ Also, to change account passwords for multiple servers through one Job, you need ### Creating Password Change Jobs
-![Administrator > Servers > Server Account Management > Password Provisioning > Create Job](/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job/image-20240831-162006.png) +Administrator > Servers > Server Account Management > Password Provisioning > Create Job
Administrator > Servers > Server Account Management > Password Provisioning > Create Job
@@ -45,7 +45,7 @@ To periodically change passwords for Provisioning Information accounts, accounts ### Creating Active Directory Password Change Jobs
-![Administrator > Servers > Server Account Management > Password Provisioning > Active Directory tab > Create Job](/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job/Screenshot-2025-07-27-at-6.26.06-PM.png) +Administrator > Servers > Server Account Management > Password Provisioning > Active Directory tab > Create Job
Administrator > Servers > Server Account Management > Password Provisioning > Active Directory tab > Create Job
diff --git a/src/content/en/administrator-manual/servers/server-account-management/server-account-templates.mdx b/src/content/en/administrator-manual/servers/server-account-management/server-account-templates.mdx index 5a284293..f639058d 100644 --- a/src/content/en/administrator-manual/servers/server-account-management/server-account-templates.mdx +++ b/src/content/en/administrator-manual/servers/server-account-management/server-account-templates.mdx @@ -13,7 +13,7 @@ Templates created in advance can be easily and conveniently loaded in servers or ### Creating Server Account Templates
-![Administrator > Servers > Server Account Management > Server Account Templates > Create Template](/administrator-manual/servers/server-account-management/server-account-templates/image-20240828-011910.png) +Administrator > Servers > Server Account Management > Server Account Templates > Create Template
Administrator > Servers > Server Account Management > Server Account Templates > Create Template
@@ -28,7 +28,7 @@ Administrator > Servers > Server Account Management > Server Account Te 5. Click the newly created template from the list. 6. Click `Add Account` in the Account item to add accounts to register in the template.
- ![Screenshot-2025-07-27-at-10.35.23-PM.png](/administrator-manual/servers/server-account-management/server-account-templates/Screenshot-2025-07-27-at-10.35.23-PM.png) + Screenshot-2025-07-27-at-10.35.23-PM.png
* For individual Account setup methods, refer to [Managing Servers as Groups](../connection-management/server-groups/managing-servers-as-groups). 7. Click `Save Changes` in the top right to save. diff --git a/src/content/en/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx b/src/content/en/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx index 818036b8..0edebc2e 100644 --- a/src/content/en/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx +++ b/src/content/en/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx @@ -13,7 +13,7 @@ Keys registered in this way can be loaded by setting Auth Type to SSH Key in the ### Registering SSH Keys
-![Administrator > Servers > Server Account Management > SSH Key Configurations > Create SSH Key](/administrator-manual/servers/server-account-management/ssh-key-configurations/image-20240828-012337.png) +Administrator > Servers > Server Account Management > SSH Key Configurations > Create SSH Key
Administrator > Servers > Server Account Management > SSH Key Configurations > Create SSH Key
@@ -33,7 +33,7 @@ Administrator > Servers > Server Account Management > SSH Key Configura ### SSH Key Management Features
-![Administrator > Servers > Server Account Management > SSH Key Configurations > SSH Key Details](/administrator-manual/servers/server-account-management/ssh-key-configurations/image-20240828-012530.png) +Administrator > Servers > Server Account Management > SSH Key Configurations > SSH Key Details
Administrator > Servers > Server Account Management > SSH Key Configurations > SSH Key Details
diff --git a/src/content/en/administrator-manual/servers/session-monitoring.mdx b/src/content/en/administrator-manual/servers/session-monitoring.mdx index ab50abc8..701d576b 100644 --- a/src/content/en/administrator-manual/servers/session-monitoring.mdx +++ b/src/content/en/administrator-manual/servers/session-monitoring.mdx @@ -18,7 +18,7 @@ From 11.5.0, Session Monitoring, which was a submenu item under Audit, has been ### Viewing Session Monitoring
-![Administrator > Servers > Monitoring > Session Monitoring](/administrator-manual/servers/session-monitoring/image-20251218-073053.png) +Administrator > Servers > Monitoring > Session Monitoring
Administrator > Servers > Monitoring > Session Monitoring
@@ -42,7 +42,7 @@ Administrator > Servers > Monitoring > Session Monitoring ### Force Terminating Sessions
-![image-20251218-073257.png](/administrator-manual/servers/session-monitoring/image-20251218-073257.png) +image-20251218-073257.png
diff --git a/src/content/en/administrator-manual/web-apps.mdx b/src/content/en/administrator-manual/web-apps.mdx index 9c59d02a..7a4c651e 100644 --- a/src/content/en/administrator-manual/web-apps.mdx +++ b/src/content/en/administrator-manual/web-apps.mdx @@ -5,7 +5,7 @@ title: 'Web Apps' # Web Apps
-![image-20241218-141244.png](/administrator-manual/web-apps/image-20241218-141244.png) +image-20241218-141244.png
### Overview diff --git a/src/content/en/administrator-manual/web-apps/connection-management/web-app-configurations.mdx b/src/content/en/administrator-manual/web-apps/connection-management/web-app-configurations.mdx index 37592b14..55918217 100644 --- a/src/content/en/administrator-manual/web-apps/connection-management/web-app-configurations.mdx +++ b/src/content/en/administrator-manual/web-apps/connection-management/web-app-configurations.mdx @@ -11,7 +11,7 @@ You can configure core elements of web application connection security such as l This allows administrators to configure web environments according to their organization's security requirements and protect systems from potential threats.
-![Administrator > Web Apps > Connection Management > Web App Configurations](/administrator-manual/web-apps/connection-management/web-app-configurations/image-20250629-153047.png) +Administrator > Web Apps > Connection Management > Web App Configurations
Administrator > Web Apps > Connection Management > Web App Configurations
diff --git a/src/content/en/administrator-manual/web-apps/connection-management/web-apps.mdx b/src/content/en/administrator-manual/web-apps/connection-management/web-apps.mdx index 059e666c..b8c4d0d4 100644 --- a/src/content/en/administrator-manual/web-apps/connection-management/web-apps.mdx +++ b/src/content/en/administrator-manual/web-apps/connection-management/web-apps.mdx @@ -12,7 +12,7 @@ QueryPie supports viewing, creating, and modifying Web Apps assets. All web apps registered through web applications, APIs, or manually registered web apps are managed on the same page.
-![Administrator > Web Apps > Connection Management > Web Apps](/administrator-manual/web-apps/connection-management/web-apps/image-20250629-153743.png) +Administrator > Web Apps > Connection Management > Web Apps
Administrator > Web Apps > Connection Management > Web Apps
@@ -36,7 +36,7 @@ Administrator > Web Apps > Connection Management > Web Apps ### Creating Web Apps
-![Administrator > Web Apps > Connection Management > Web Apps](/administrator-manual/web-apps/connection-management/web-apps/Screenshot-2025-08-27-at-6.58.08-PM.png) +Administrator > Web Apps > Connection Management > Web Apps
Administrator > Web Apps > Connection Management > Web Apps
@@ -56,7 +56,7 @@ Administrator > Web Apps > Connection Management > Web Apps ### Setting Web App Owners and Members
-![Administrator > Web Apps > Connection Management > Web Apps > Web App Owners](/administrator-manual/web-apps/connection-management/web-apps/Screenshot-2025-08-27-at-6.57.07-PM.png) +Administrator > Web Apps > Connection Management > Web Apps > Web App Owners
Administrator > Web Apps > Connection Management > Web Apps > Web App Owners
@@ -70,7 +70,7 @@ The permissions for each role are clearly separated as follows. * One user can have both Owner and Member permissions simultaneously, in which case both request submission and approval are possible.
-![Assign Owners screen](/administrator-manual/web-apps/connection-management/web-apps/Screenshot-2025-08-27-at-6.57.24-PM.png) +Assign Owners screen
Assign Owners screen
diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart.mdx index c41e36ef..837951c8 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart.mdx @@ -48,7 +48,7 @@ In this quickstart guide, we will register only some of these paths under the we 2. Click the `Create a Web App` button to enter the web app registration page.
-![Admin > Web Apps > Create a Web App](/administrator-manual/web-apps/wac-quickstart/screenshot-20250412-225620.png) +Admin > Web Apps > Create a Web App
Admin > Web Apps > Create a Web App
@@ -95,7 +95,7 @@ Then enter the remaining information. Next, let's create a policy that only allows access to registered sub-paths for the QueryPie website.
-![Admin > Web Apps > Web App Access Control > Policies > Edit Policy Code](/administrator-manual/web-apps/wac-quickstart/screenshot-20250412-230727.png) +Admin > Web Apps > Web App Access Control > Policies > Edit Policy Code
Admin > Web Apps > Web App Access Control > Policies > Edit Policy Code
@@ -131,7 +131,7 @@ spec: Now let's create a new role and assign the policy we created earlier.
-![Admin > Web Apps > Web App Access Control > Roles > List Details](/administrator-manual/web-apps/wac-quickstart/screenshot-20250330-204911.png) +Admin > Web Apps > Web App Access Control > Roles > List Details
Admin > Web Apps > Web App Access Control > Roles > List Details
@@ -148,7 +148,7 @@ Admin > Web Apps > Web App Access Control > Roles > List Details Now let's assign the QP Web Test role we just created to the current user.
-![Admin > Web Apps > Web App Access Control > Access Control > List Details](/administrator-manual/web-apps/wac-quickstart/screenshot-20250330-204937.png) +Admin > Web Apps > Web App Access Control > Access Control > List Details
Admin > Web Apps > Web App Access Control > Access Control > List Details
@@ -169,14 +169,14 @@ Now let's proceed with user-side settings to verify that the access policy we ju 1. While logged into QueryPie, click the profile button in the top right and click Support > Download Web Secure button in the profile menu.

- ![QueryPie > Profile Menu](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-120321.png) + QueryPie > Profile Menu
QueryPie > Profile Menu
2. The QueryPie Web Secure Download modal opens. In **A. Install Root CA Certificate**, click Step 1. Download Link to download the certificate file.

- ![QueryPie Web Secure Download](/administrator-manual/web-apps/wac-quickstart/screenshot-20250116-155957.png) + QueryPie Web Secure Download
QueryPie Web Secure Download
@@ -194,7 +194,7 @@ Now let's proceed with user-side settings to verify that the access policy we ju 2. Enable the Developer mode toggle in the top right of the page. 3. Drag the Extension file you received **without extracting** into the extensions area.

- ![Chrome > Extensions Management](/administrator-manual/web-apps/wac-quickstart/screenshot-20241219-192626.png) + Chrome > Extensions Management
Chrome > Extensions Management
@@ -202,7 +202,7 @@ Now let's proceed with user-side settings to verify that the access policy we ju 4. The Host Configuration page opens in a new tab. Paste the QueryPie address you are currently using in QueryPie Host and click the `Continue` button. 1. If the Host information is valid, the `Go to Dashboard` button appears. Click it to enter QueryPie in a new tab.
- ![Host Configuration Page](/administrator-manual/web-apps/wac-quickstart/screenshot-20241219-192931.png) + Host Configuration Page
Host Configuration Page
@@ -225,14 +225,14 @@ Please close all existing browser tabs and windows before installing the extensi 3. When the Role selection modal appears, select QP Web Test. 2. In the Web App Dashboard's My Apps, you will see the QueryPie Web Site app icon you registered earlier. Click the icon to access the website.

- ![QueryPie > Web Apps > Web App Dashboard](/administrator-manual/web-apps/wac-quickstart/screenshot-20250412-224323.png) + QueryPie > Web Apps > Web App Dashboard
QueryPie > Web Apps > Web App Dashboard
3. On first access, you will see a screen informing you that the current web session is being recorded. Click the `Continue` button to access the website.

- ![Web Session Monitoring Notification](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-113541.png) + Web Session Monitoring Notification
Web Session Monitoring Notification
@@ -240,7 +240,7 @@ Please close all existing browser tabs and windows before installing the extensi 4. You can see that Watermark has been applied to the QueryPie homepage.
5. When trying to access unauthorized pages (e.g., Products menu), you will be redirected to a blocking notification screen.
- ![ QueryPie Access Denied](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-113037.png) + QueryPie Access Denied
QueryPie Access Denied
@@ -252,7 +252,7 @@ Please close all existing browser tabs and windows before installing the extensi
-![Admin > Audit > Web Apps > Web Access History](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-115604.png) +Admin > Audit > Web Apps > Web Access History
Admin > Audit > Web Apps > Web Access History
@@ -281,7 +281,7 @@ Records are only created when User Activity Recording is enabled during Web App
-![Admin > Audit > Web Apps > User Activity Recordings > Details](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-115805.png) +Admin > Audit > Web Apps > User Activity Recordings > Details
Admin > Audit > Web Apps > User Activity Recordings > Details
diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx index 34cbaede..67d9401d 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx @@ -32,7 +32,7 @@ To follow this guide, you need Owner or Web App Admin permissions among QueryPie 2. Click the `Create a Web App` button to enter the web app registration page.
-![screenshot-20250412-225620.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/screenshot-20250412-225620.png) +screenshot-20250412-225620.png
Enter the following information. @@ -56,7 +56,7 @@ Enter the following information. ### 2. Register Web App Owner / Member
-![image-20250513-042540.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-042540.png) +image-20250513-042540.png
1. Access the web app detail page @@ -84,7 +84,7 @@ Please refer to the following manual for installation methods.
-![image-20250513-065134.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-065134.png) +image-20250513-065134.png
1. After accessing QueryPie, click Web Apps at the top. @@ -94,7 +94,7 @@ Please refer to the following manual for installation methods.
-![image-20250513-065247.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-065247.png) +image-20250513-065247.png
1. Access Web App Just-In-Time Access Request. @@ -118,7 +118,7 @@ When requesting JIT (Just-in-Time) permissions, there are the following constrai ### 4. Approver's JIT Web App Access Permission Request Approval
-![image-20250513-072925.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-072925.png) +image-20250513-072925.png
1. A user with approval authority (designated as Web App Owner) accesses Workflow. @@ -130,7 +130,7 @@ When requesting JIT (Just-in-Time) permissions, there are the following constrai ### 5. Access Web App through QueryPie
-![image-20250513-073501.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-073501.png) +image-20250513-073501.png
1. Go to QueryPie Web Apps. diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx index 06a3c0df..b270c129 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx @@ -14,7 +14,7 @@ The Web App Configurations page is available in version 10.2.6 or higher. You can perform initial WAC-related settings through the GUI on the Web App Configurations page.
-![Admin > Web Apps > Connection Management > Web App Configurations](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250413-224538.png) +Admin > Web Apps > Connection Management > Web App Configurations
Admin > Web Apps > Connection Management > Web App Configurations
@@ -63,7 +63,7 @@ Current Version and Minimum Required Version information must be entered accordi 2. In a closed network environment, access QueryPie > Web App Configurations page, then click the `Edit` button in the QueryPie Web Secure (Extension) Configurations section. 3. In the Extension File option, select `Add by File Upload` and upload the extension file you downloaded.
- ![Admin > Web Apps > Connection Management > Web App Configurations > WAC Secure settings modal](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250310-160708.png) + Admin > Web Apps > Connection Management > Web App Configurations > WAC Secure settings modal
Admin > Web Apps > Connection Management > Web App Configurations > WAC Secure settings modal
@@ -88,7 +88,7 @@ In the Watermark Configurations section, you can check the currently applied wat 1. Click the `Edit` button to change the text settings. 2. When the settings modal is open, you can preview the watermark application results based on the currently logged-in user.

- ![Admin > Web Apps > Connection Management > Web App Configurations > Watermark settings modal](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250310-161723.png) + Admin > Web Apps > Connection Management > Web App Configurations > Watermark settings modal
Admin > Web Apps > Connection Management > Web App Configurations > Watermark settings modal
@@ -103,7 +103,7 @@ In the Watermark Configurations section, you can check the currently applied wat In the Root CA Certificate Configurations section, you can backup and restore the Root CA certificate currently used by QueryPie.
-![Admin > Web Apps > Connection Management > Web App Configurations > Manage .cer file modal](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250413-225409.png) +Admin > Web Apps > Connection Management > Web App Configurations > Manage .cer file modal
Admin > Web Apps > Connection Management > Web App Configurations > Manage .cer file modal
diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx index dba42550..d221ee80 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx @@ -31,12 +31,12 @@ You can install the Root CA certificate in the Keychain Access app. 2. Drag and drop the downloaded certificate file onto the Keychain Access app screen. The newly installed querypie certificate is not in a trusted state. 3. Double-click the querypie certificate to open the modal, click the Trust item to expand the collapsed area, then change **When using this certificate** : `Use system defaults` to `Always trust` and close the modal.
- ![screenshot-20250113-201320.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-201320.png) + screenshot-20250113-201320.png
4. Perform additional authentication to change system certificate trust settings. 5. The newly installed querypie certificate is displayed as trusted for all users.
- ![screenshot-20250113-201143.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-201143.png) + screenshot-20250113-201143.png
Alternatively, you can set the same configuration by running the following command in Terminal. @@ -53,24 +53,24 @@ You can install the Root CA certificate through the Certificate Import Wizard. 2. Right-click on the certificate file and select `Install Certificate(I)` from the context menu to start the Certificate Import Wizard. 3. When the Certificate Import Wizard window opens, select `Current User(C)` for the storage location and click the `Next(N)` button.
- ![screenshot-20250113-202645.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-202645.png) + screenshot-20250113-202645.png
4. For the certificate store, select the `Place all certificates in the following store(P)` option and click the `Browse(R)...` button. 5. When the **Select Certificate Store** modal opens, select Trusted Root Certification Authorities. Keep the actual store display option unchecked. Click the OK button.
- ![screenshot-20250113-202727.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-202727.png) + screenshot-20250113-202727.png
6. Confirm the certificate store settings and click the `Next(N)` button.
- ![screenshot-20250113-202738.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-202738.png) + screenshot-20250113-202738.png
7. Confirm the set content and click the `Finish(F)` button.
- ![screenshot-20250113-203130.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-203130.png) + screenshot-20250113-203130.png
8. A security warning modal appears. Click the `Yes(Y)` button to immediately execute certificate import. Click the OK button in the import completion modal.
- ![screenshot-20250113-203453.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-203453.png) + screenshot-20250113-203453.png
### 3. Verify Chrome Certificate Settings diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx index e738a3ed..d0165a65 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx @@ -19,7 +19,7 @@ By comparing the currently used extension version with the minimum required vers #### When does the recording notification modal appear? It seems to appear every time.
-![image-20250414-105519.png](/administrator-manual/web-apps/wac-quickstart/wac-faq/image-20250414-105519.png) +image-20250414-105519.png
The recording notification modal appears at the start of a session. @@ -46,7 +46,7 @@ However, if other events (such as mouse clicks) occur, screenshots are immediate #### The extension's user information shows N/A and doesn't change even after refreshing.
-![image-20250415-071521.png](/administrator-manual/web-apps/wac-quickstart/wac-faq/image-20250415-071521.png) +image-20250415-071521.png
This occurs because the extension login has expired. diff --git a/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx b/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx index ffaa406b..4d455165 100644 --- a/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx +++ b/src/content/en/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx @@ -16,7 +16,7 @@ To prevent such situations, please close all existing browser tabs and windows b #### When WebApp access fails and the browser displays an `ERR_TIMED_OUT` error message
-![image-20250401-011848.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-011848.png) +image-20250401-011848.png
This may be a phenomenon that occurs when the browser cannot connect to the WAC Proxy. @@ -24,7 +24,7 @@ This may be a phenomenon that occurs when the browser cannot connect to the WAC First, check if the WAC Proxy address is properly set in the Admin > Web Apps > Web app Configuration menu.
-![image-20250401-012042.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-012042.png) +image-20250401-012042.png
Run the following command in the local terminal of the browser where the problem occurred to check if the connection to WAC Proxy is working. @@ -83,7 +83,7 @@ If the same issue persists even after proceeding this far, Chrome browser networ * Open `chrome://net-export/` in Chrome browser and click Start Over. (Select the default option `Strip private information`.)
-![image-20250401-012452.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-012452.png) +image-20250401-012452.png
* Enter the WebApp address that cannot be accessed in Chrome browser and navigate to it. @@ -97,7 +97,7 @@ If the same issue persists even after proceeding this far, Chrome browser networ * Check network transmission and reception content in the Events menu on the left.
-![image-20250401-012759.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-012759.png) +image-20250401-012759.png
@@ -144,10 +144,10 @@ This guide explains how to extract related logs when problems occur with QueryPi 1. Click `QueryPie Web Secure` from the panel list.
- ![screenshot-20250116-134315.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/screenshot-20250116-134315.png) + screenshot-20250116-134315.png
2. The log extraction function runs in developer tools. Click the `Export Log` button to save the querypie-web-secure-logs.json file separately. Click the `Save` button.
- ![screenshot-20250116-134632.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/screenshot-20250116-134632.png) + screenshot-20250116-134632.png
3. Attach the saved log when making a CS request. diff --git a/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control.mdx b/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control.mdx index 7ffaf2b0..19bff86e 100644 --- a/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control.mdx +++ b/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control.mdx @@ -10,7 +10,7 @@ Supports granting and revoking management of access permissions to web applicati Access Control represents the final step for implementing and applying web app access permissions.
-![Administrator > Web Apps > Web App Access Control > Access Control](/administrator-manual/web-apps/web-app-access-control/access-control/image-20250629-155857.png) +Administrator > Web Apps > Web App Access Control > Access Control
Administrator > Web Apps > Web App Access Control > Access Control
@@ -20,7 +20,7 @@ Administrator > Web Apps > Web App Access Control > Access Control ### Viewing Access Control Status
-![Administrator > Web Apps > Web App Access Control > Access Control > List Details](/administrator-manual/web-apps/web-app-access-control/access-control/Screenshot-2025-08-25-at-9.37.07-PM.png) +Administrator > Web Apps > Web App Access Control > Access Control > List Details
Administrator > Web Apps > Web App Access Control > Access Control > List Details
@@ -33,7 +33,7 @@ Administrator > Web Apps > Web App Access Control > Access Control > 5. Clicking a row in the Access Control list navigates to the detailed page for the target user/group. 1. **Roles**
- ![image-20250629-160303.png](/administrator-manual/web-apps/web-app-access-control/access-control/image-20250629-160303.png) + image-20250629-160303.png
1. This is the default tab where you can view the list of assigned Roles. 2. You can search by Role name. @@ -58,7 +58,7 @@ Administrator > Web Apps > Web App Access Control > Access Control > 2. Click the Revoke button located in the top left of the list. 3. When the permission revocation confirmation window appears, check the content and click the confirmation button to finally revoke the permissions.
- ![image-20250617-151613.png](/administrator-manual/web-apps/web-app-access-control/access-control/image-20250617-151613.png) + image-20250617-151613.png
3. **Web Apps** 1. Lists the web application list accessible by assigned Roles. diff --git a/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx b/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx index 5c0c1506..d0d10365 100644 --- a/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx +++ b/src/content/en/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx @@ -15,7 +15,7 @@ Administrators can grant or revoke roles (Roles) with server access permissions #### 1. Select the target to grant permissions to.
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161238.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
@@ -28,13 +28,13 @@ Administrator > Servers > Server Access Control > Access Control #### 2. Select the Role to grant permissions to.
-![image-20250629-161326.png](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161326.png) +image-20250629-161326.png
1. Select the Roles tab on the left side of the screen. 2. Click the `+ Grant Roles` button in the center right.
- ![image-20250629-161407.png](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161407.png) + image-20250629-161407.png
3. Check the checkbox on the left of the Role to grant. 4. Enter the Expiration Date. The default value is 1 year. @@ -44,7 +44,7 @@ Administrator > Servers > Server Access Control > Access Control ### Revoking Roles
-![image-20250629-161437.png](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161437.png) +image-20250629-161437.png
1. Navigate to Administrator > Web Apps > Web App Access Control > Access Control menu. diff --git a/src/content/en/administrator-manual/web-apps/web-app-access-control/policies.mdx b/src/content/en/administrator-manual/web-apps/web-app-access-control/policies.mdx index bf8c8c75..0a821957 100644 --- a/src/content/en/administrator-manual/web-apps/web-app-access-control/policies.mdx +++ b/src/content/en/administrator-manual/web-apps/web-app-access-control/policies.mdx @@ -12,7 +12,7 @@ Supports viewing, creating, modifying, and deleting access policies (Policy) for Policy is the core foundational step for implementing and applying web application access permissions.
-![Administrator > Web Apps > Web App Access Control > Policies](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164449.png) +Administrator > Web Apps > Web App Access Control > Policies
Administrator > Web Apps > Web App Access Control > Policies
@@ -21,7 +21,7 @@ Administrator > Web Apps > Web App Access Control > Policies ### Viewing Policies
-![Administrator > Web Apps > Web App Access Control > Policies > List Details](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164509.png) +Administrator > Web Apps > Web App Access Control > Policies > List Details
Administrator > Web Apps > Web App Access Control > Policies > List Details
@@ -35,13 +35,13 @@ Administrator > Web Apps > Web App Access Control > Policies > List 6. Clicking each row allows you to view policy detailed information. 1. Detail
- ![image-20250629-164600.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164600.png) + image-20250629-164600.png
1. This is the default tab where you can view the code defined by the policy. 2. There is a `Go to Editor Mode` button on the right of the Detail tab, and clicking it switches to the corresponding Code Editor page screen. 2. Roles
- ![image-20250629-164733.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164733.png) + image-20250629-164733.png
1. Lists the Role list where this policy is assigned. 2. The list displays the following information for each Role: @@ -52,7 +52,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List 3. Clicking each row provides detailed information about the Role in drawer format. 3. Versions
- ![image-20250629-164755.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164755.png) + image-20250629-164755.png
1. Lists the history for each version of this policy. 1. Policy versions are updated when Code is modified and saved. @@ -72,7 +72,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Creating Policies
-![image-20250629-164901.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164901.png) +image-20250629-164901.png
1. Navigate to Administrator > Web Apps > Web App Access Control > Policies menu. @@ -85,7 +85,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Modifying Policies
-![image-20250629-164928.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164928.png) +image-20250629-164928.png
@@ -97,7 +97,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Duplicating Policies
-![image-20250629-164941.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164941.png) +image-20250629-164941.png
1. Navigate to Administrator > Web Apps > Web App Access Control > Policies menu. @@ -109,7 +109,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Deleting Policies
-![image-20250629-164955.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164955.png) +image-20250629-164955.png
1. Navigate to Administrator > Web Apps > Web App Access Control > Policies menu. @@ -123,7 +123,7 @@ When deleting a Policy, it is automatically separated from web application resou ### Editing Policy Code
-![image-20250629-165051.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-165051.png) +image-20250629-165051.png
1. Navigate to Administrator > Web Apps > Web App Access Control > Policies menu. diff --git a/src/content/en/administrator-manual/web-apps/web-app-access-control/roles.mdx b/src/content/en/administrator-manual/web-apps/web-app-access-control/roles.mdx index a1e54d5b..a24c179f 100644 --- a/src/content/en/administrator-manual/web-apps/web-app-access-control/roles.mdx +++ b/src/content/en/administrator-manual/web-apps/web-app-access-control/roles.mdx @@ -12,7 +12,7 @@ Supports viewing, creating, modifying, and deleting roles (Role) according to ac Role is the step after Policy for implementing and applying web app access permissions, meaning a collection of Policies and permissions that serve as a link between users/groups and policies.
-![Administrator > Web Apps > Web App Access Control > Roles](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-161837.png) +Administrator > Web Apps > Web App Access Control > Roles
Administrator > Web Apps > Web App Access Control > Roles
@@ -22,7 +22,7 @@ Administrator > Web Apps > Web App Access Control > Roles ### Viewing Roles
-![Administrator > Web Apps > Web App Access Control > Roles > List Details](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-161857.png) +Administrator > Web Apps > Web App Access Control > Roles > List Details
Administrator > Web Apps > Web App Access Control > Roles > List Details
@@ -35,7 +35,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 5. Clicking each row allows you to view role detailed information. 1. **Policies**
- ![image-20250629-163153.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163153.png) + image-20250629-163153.png
1. This is the default tab where you can view the list of assigned policies. 2. The table list displays the following information for each policy: @@ -46,7 +46,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 5. Assigned By : Administrator name who assigned this policy 3. Clicking the left of each policy row provides detailed information about the policy in drawer format.
- ![image-20250629-163327.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163327.png) + image-20250629-163327.png
1. Basic information is displayed at the top as follows: 1. **Name** : Policy name @@ -58,7 +58,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 2. The policy is displayed as code at the bottom. 2. **Users/Groups**
- ![image-20250629-163722.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163722.png) + image-20250629-163722.png
1. Lists the user/group list where this Role is assigned. 2. You can search by user/group name. @@ -70,7 +70,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 5. Granted At : Date and time when this Role was assigned to the user/group 3. **Web Apps**
- ![image-20250629-163658.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163658.png) + image-20250629-163658.png
1. Lists the web application list accessible by this Role. 2. You can search by web application name. @@ -96,7 +96,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det ### Modifying Roles
-![image-20250629-163924.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163924.png) +image-20250629-163924.png
1. Navigate to Administrator > Web Apps > Access Control > Roles menu. @@ -107,7 +107,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det ### Deleting Roles
-![image-20250629-163949.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163949.png) +image-20250629-163949.png
1. Navigate to Administrator > Web Apps > Access Control > Roles menu. diff --git a/src/content/en/installation.mdx b/src/content/en/installation.mdx index ec4bbe52..17feaf64 100644 --- a/src/content/en/installation.mdx +++ b/src/content/en/installation.mdx @@ -9,11 +9,11 @@ For installation instance specifications, we recommend 4 vCPUs, 16 GiB Memory, a For detailed installation instructions, please refer to the following documents: -* [Prerequisites](installation/prerequisites) -* [Installation](installation/installation) -* [System Architecture and Network Access Control](installation/system-architecture-and-network-access-control) -* [Container Environment Variables](installation/container-environment-variables) -* [License Installation](installation/license-installation) -* [Server Configuration Requirements](installation/server-configuration-requirements) -* [QueryPie ACP Community Edition](installation/querypie-acp-community-edition) - * [MCP Configuration Guide](installation/querypie-acp-community-edition/mcp-configuration-guide) +* [설치 전 준비사항](#unexpected-failure) +* [설치하기](#unexpected-failure) +* [시스템 아키텍처와 네트워크 접근제어](#unexpected-failure) +* [컨테이너 환경변수](#unexpected-failure) +* [라이선스 설치](#unexpected-failure) +* [서버구성 요구사항](#unexpected-failure) +* [QueryPie ACP Community Edition](#unexpected-failure) + * [MCP 설정 가이드](#unexpected-failure) diff --git a/src/content/en/installation/container-environment-variables.mdx b/src/content/en/installation/container-environment-variables.mdx index 661065e7..6efe07b4 100644 --- a/src/content/en/installation/container-environment-variables.mdx +++ b/src/content/en/installation/container-environment-variables.mdx @@ -209,7 +209,7 @@ The Account ID value shown in the screenshot below is the value provided from th It is used in the Account ID section as shown in the figure below.
-![image-20241031-062026.png](/installation/container-environment-variables/image-20241031-062026.png) +image-20241031-062026.png
diff --git a/src/content/en/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx b/src/content/en/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx index a911879d..a0fcffef 100644 --- a/src/content/en/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx +++ b/src/content/en/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx @@ -125,7 +125,7 @@ This problem occurs when the number of DB connections required by QueryPie Serve You will encounter the error message `[API] Could not open JPA EntityManager for transaction` in the Web Console.
-![[API] Could not open JPA EntityManager for transaction](/installation/container-environment-variables/optimizing-dbmaxconnectionsize/Screenshot-2025-04-24-at-9.38.20-PM.png) +[API] Could not open JPA EntityManager for transaction
[API] Could not open JPA EntityManager for transaction
diff --git a/src/content/en/installation/container-environment-variables/querypieweburl.mdx b/src/content/en/installation/container-environment-variables/querypieweburl.mdx index 6e52b7a4..0b6440a3 100644 --- a/src/content/en/installation/container-environment-variables/querypieweburl.mdx +++ b/src/content/en/installation/container-environment-variables/querypieweburl.mdx @@ -16,7 +16,7 @@ QUERYPIE_WEB_URL is used in various paths such as service access, authentication **Starting from QueryPie version 10.2.8, this environment variable is no longer used. It has been replaced by Web Base URL in the General menu.**
-![screenshot-20250312-112533.png](/installation/container-environment-variables/querypieweburl/screenshot-20250312-112533.png) +screenshot-20250312-112533.png
diff --git a/src/content/en/installation/installation/installation-guide-setupv2sh.mdx b/src/content/en/installation/installation/installation-guide-setupv2sh.mdx index e1628bc0..ad2f3af9 100644 --- a/src/content/en/installation/installation/installation-guide-setupv2sh.mdx +++ b/src/content/en/installation/installation/installation-guide-setupv2sh.mdx @@ -169,7 +169,7 @@ You may need to change Firewall, AWS Security Group settings, etc. by referring License files can be entered on the web console screen.
-![Enter the license in PEM format.](/installation/installation/installation-guide-setupv2sh/image-20250718-063723.png) +Enter the license in PEM format.
Enter the license in PEM format.
@@ -199,7 +199,7 @@ This URL is used for the following purposes.
-![image-20250520-081112.png](/installation/installation/installation-guide-setupv2sh/image-20250520-081112.png) +image-20250520-081112.png
### Product-Specific Settings @@ -239,7 +239,7 @@ After registering the address for Proxy access in QueryPie Database, you do not When you attempt to log in from User Agent, after authentication through a web browser, you can use User Agent.
-![image-20250520-082706.png](/installation/installation/installation-guide-setupv2sh/image-20250520-082706.png) +image-20250520-082706.png
#### KAC: Proxy Access Address Settings @@ -258,7 +258,7 @@ UPDATE querypie.k_proxy_setting SET host = 'https://'; ```
-![image-20250520-084243.png](/installation/installation/installation-guide-setupv2sh/image-20250520-084243.png) +image-20250520-084243.png
diff --git a/src/content/en/installation/installation/installation-guide-simple-configuration.mdx b/src/content/en/installation/installation/installation-guide-simple-configuration.mdx index 97ffb682..596d0e0b 100644 --- a/src/content/en/installation/installation/installation-guide-simple-configuration.mdx +++ b/src/content/en/installation/installation/installation-guide-simple-configuration.mdx @@ -314,7 +314,7 @@ This URL is used for the following purposes. * For other detailed purposes, please refer to [https://chequer.atlassian.net/wiki/spaces/QCP/pages/876937310](https://chequer.atlassian.net/wiki/spaces/QCP/pages/876937310).
-![image-20250520-081112.png](/installation/installation/installation-guide-simple-configuration/image-20250520-081112.png) +image-20250520-081112.png
### Product-Specific Settings @@ -354,7 +354,7 @@ After registering the address for Proxy access in QueryPie Database, you do not When you attempt to log in from User Agent, after authentication through a web browser, you can use User Agent.
-![image-20250520-082706.png](/installation/installation/installation-guide-simple-configuration/image-20250520-082706.png) +image-20250520-082706.png
#### KAC: Proxy Access Address Settings @@ -373,7 +373,7 @@ UPDATE querypie.k_proxy_setting SET host = 'https://'; ```
-![image-20250520-084243.png](/installation/installation/installation-guide-simple-configuration/image-20250520-084243.png) +image-20250520-084243.png
#### WAC: Proxy Access Address Settings diff --git a/src/content/en/installation/querypie-acp-community-edition.mdx b/src/content/en/installation/querypie-acp-community-edition.mdx index a9740caa..0813f1d8 100644 --- a/src/content/en/installation/querypie-acp-community-edition.mdx +++ b/src/content/en/installation/querypie-acp-community-edition.mdx @@ -94,7 +94,7 @@ bash <(curl -s https://dl.querypie.com/setup.v2.sh) ⏱️ Installation usually takes about **7~10 minutes**.
-![Screen showing installation has started](/installation/querypie-acp-community-edition/image-20250718-063107.png) +Screen showing installation has started
Screen showing installation has started
@@ -102,7 +102,7 @@ Screen showing installation has started
-![Screen showing installation has completed](/installation/querypie-acp-community-edition/image-20250718-063140.png) +Screen showing installation has completed
Screen showing installation has completed
@@ -129,7 +129,7 @@ The IP address of the Linux server where QueryPie is installed must be accessibl Upload the `.crt` file received by email, or copy and paste the PEM format text content.
-![License input screen in PEM format](/installation/querypie-acp-community-edition/image-20250718-063723.png) +License input screen in PEM format
License input screen in PEM format
@@ -154,7 +154,7 @@ After setting a new password, you can use the service. * Password: `querypie`
-![Initial login screen](/installation/querypie-acp-community-edition/image-20260107-080840.png) +Initial login screen
Initial login screen
@@ -163,7 +163,7 @@ Initial login screen After logging in with the qp-admin account, change the default password to a different password.
-![Initial password change screen](/installation/querypie-acp-community-edition/image-20260107-080542.png) +Initial password change screen
Initial password change screen
@@ -175,7 +175,7 @@ Installation has been successfully completed. Please refer to the administrator manual for environment configuration: [Administrator Manual](../administrator-manual)
To navigate to the administrator page, click the `Go to Admin Page` button in the top right corner.
-![User dashboard displayed after login](/installation/querypie-acp-community-edition/image-20260107-081618.png) +User dashboard displayed after login
User dashboard displayed after login
@@ -208,7 +208,7 @@ docker compose --profile=app exec app readyz If started normally, a screen similar to the following will be displayed.
-![When started normally](/installation/querypie-acp-community-edition/image-20260107-083457.png) +When started normally
When started normally
@@ -239,7 +239,7 @@ If you have questions about QueryPie Community installation and use, you can con By following the procedure below to set up the **QueryPie Customer Center** preset in MCP, you can receive support directly in the chat window.
-![image-20250718-070933.png](/installation/querypie-acp-community-edition/image-20250718-070933.png) +image-20250718-070933.png
1. Integration tab → Click Install QueryPie Customer Center. diff --git a/src/content/en/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx b/src/content/en/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx index 1dab2b4d..bf12c820 100644 --- a/src/content/en/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx +++ b/src/content/en/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx @@ -56,7 +56,7 @@ claude mcp add querypie --transport http {QuerPie_URL}/api/mcp Example: `claude mcp add querypie --transport http https://querypie.example.com/api/mcp`
-![Add MCP server](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-091753.png) +Add MCP server
Add MCP server
@@ -67,28 +67,28 @@ Add MCP server First, enter `/mcp` to check the status of currently configured MCP Servers.
-![image-20251211-092208.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092208.png) +image-20251211-092208.png
Select `querypie` from the list. Then, select `Authenticate`.
-![image-20251211-092454.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092454.png) +image-20251211-092454.png
When the browser opens, log in on the QueryPie login page. If login is successful, the browser will display "Authentication Successful".
-![image-20251211-092741.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092741.png) +image-20251211-092741.png
Claude Code will also display "Authentication successful. Connect to querypie." message.
-![image-20251211-092842.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092842.png) +image-20251211-092842.png
@@ -97,7 +97,7 @@ Connect to querypie." message. If Claude Code is not running, you can verify the MCP connection with the `claude mcp list` command.
-![Result of executing claude mcp list command](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251214-232657.png) +Result of executing claude mcp list command
Result of executing claude mcp list command
@@ -106,7 +106,7 @@ Result of executing claude mcp list command Try performing tasks through queries.
-![Query example](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251214-232033.png) +Query example
Query example
@@ -116,7 +116,7 @@ When available tools are confirmed, a query about proceeding will be displayed. Select 'yes' or 'yes, and don't ask again for querypie -…'.
-![Response example](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251214-232144.png) +Response example
Response example
@@ -146,7 +146,7 @@ Edit configuration file: Edit the `~/.gemini/settings.json` file. Servers that support OAuth are automatically detected.
-![image-20251211-102950.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-102950.png) +image-20251211-102950.png
##### 2. Perform OAuth login. @@ -160,11 +160,11 @@ When the browser opens, log in on the QueryPie login page. If login is successful, the browser will display "Authentication Successful".
-![image-20251211-104053.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-104053.png) +image-20251211-104053.png
-![image-20251211-103846.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-103846.png) +image-20251211-103846.png
If the browser does not open automatically, you can also proceed by copying and pasting the address displayed on the screen into your browser, as shown in the figure above. @@ -197,7 +197,7 @@ Edit configuration file: Create or edit the `~/.cursor/mcp.json` file: Check in Cursor Settings that MCP tools are properly integrated.
-![image-20251212-012243.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251212-012243.png) +image-20251212-012243.png
______ @@ -228,7 +228,7 @@ Create or edit configuration file: `~/.codeium/windsurf/mcp_config.json` Check in the Windsurf Agents screen that MCP tools are properly integrated.
-![image-20251212-012554.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251212-012554.png) +image-20251212-012554.png
diff --git a/src/content/en/installation/system-architecture-and-network-access-control.mdx b/src/content/en/installation/system-architecture-and-network-access-control.mdx index 18a5887e..412cdf3f 100644 --- a/src/content/en/installation/system-architecture-and-network-access-control.mdx +++ b/src/content/en/installation/system-architecture-and-network-access-control.mdx @@ -15,7 +15,7 @@ This system architecture is for the case of installing QueryPie Service on a sin It does not include web services with TLS certificates applied, multi-configuration for high availability, etc.
-![Overview of QueryPie System Architecture ](/installation/system-architecture-and-network-access-control/image-20251204-043839.png) +Overview of QueryPie System Architecture
Overview of QueryPie System Architecture
diff --git a/src/content/en/overview.mdx b/src/content/en/overview.mdx index 409a0085..3f637326 100644 --- a/src/content/en/overview.mdx +++ b/src/content/en/overview.mdx @@ -13,7 +13,7 @@ It also offers user- and admin-friendly features that improve productivity. Manage your dispersed assets and permissions in one place with QueryPie ACP.
-![How QueryPie Access Control Platform Works](/overview/QueryPie-ACP-Overview.png) +How QueryPie Access Control Platform Works
How QueryPie Access Control Platform Works
diff --git a/src/content/en/overview/proxy-management.mdx b/src/content/en/overview/proxy-management.mdx index 9c2e7491..0cb53fda 100644 --- a/src/content/en/overview/proxy-management.mdx +++ b/src/content/en/overview/proxy-management.mdx @@ -14,7 +14,7 @@ When accessing through external clients, all access to resources can be controll ### QueryPie Proxy Introduction
-![proxy-introduction.png](/overview/proxy-management/proxy-introduction.png) +proxy-introduction.png
* **Enhanced Security** : The proxy function acts as a security intermediary between users and resources, adding a security layer against unauthorized access and potential security breaches. @@ -26,7 +26,7 @@ When accessing through external clients, all access to resources can be controll ### How QueryPie Proxy Works
-![proxy-operation-flow.png](/overview/proxy-management/proxy-operation-flow.png) +proxy-operation-flow.png
1. **Proxy Configuration** : Administrators configure whether to use proxy for each resource within QueryPie's interface. diff --git a/src/content/en/overview/proxy-management/enable-database-proxy.mdx b/src/content/en/overview/proxy-management/enable-database-proxy.mdx index 889c7fff..f14cdea0 100644 --- a/src/content/en/overview/proxy-management/enable-database-proxy.mdx +++ b/src/content/en/overview/proxy-management/enable-database-proxy.mdx @@ -20,7 +20,7 @@ By default, the Proxy usage option is disabled. Enable the Proxy usage option for connections that allow access.
-![Administrator > Databases > Connection Management > DB Connections > Connection Details > Proxy Usage](/overview/proxy-management/enable-database-proxy/image-20240725-070857.png) +Administrator > Databases > Connection Management > DB Connections > Connection Details > Proxy Usage
Administrator > Databases > Connection Management > DB Connections > Connection Details > Proxy Usage
@@ -47,7 +47,7 @@ Users of version 10.3.0 and later should refer to [Proxy Management](../../admin
-![Administrator > Databases > Connection Management > DB Connections > Proxy Management](/overview/proxy-management/enable-database-proxy/image-20240725-071030.png) +Administrator > Databases > Connection Management > DB Connections > Proxy Management
Administrator > Databases > Connection Management > DB Connections > Proxy Management
diff --git a/src/content/en/overview/system-architecture-overview.mdx b/src/content/en/overview/system-architecture-overview.mdx index 421dde65..5f4eba21 100644 --- a/src/content/en/overview/system-architecture-overview.mdx +++ b/src/content/en/overview/system-architecture-overview.mdx @@ -23,7 +23,7 @@ For customers who want to try out the product, we offer the Community Edition: [ ### Simple Configuration for Trial Evaluation
-![Simple System Configuration for Evaluation](/overview/system-architecture-overview/screenshot-20240801-115045.png) +Simple System Configuration for Evaluation
Simple System Configuration for Evaluation
@@ -59,7 +59,7 @@ The following preparations are necessary to install QueryPie for testing and eva ### Summary of System Configuration for Real Use
-![Summary of System Architecture for Real Use](/overview/system-architecture-overview/screenshot-20240801-115343.png) +Summary of System Architecture for Real Use
Summary of System Architecture for Real Use
diff --git a/src/content/en/release-notes/9120-91214/menu-improvement-guide-9120.mdx b/src/content/en/release-notes/9120-91214/menu-improvement-guide-9120.mdx index c3c7d14c..574efa37 100644 --- a/src/content/en/release-notes/9120-91214/menu-improvement-guide-9120.mdx +++ b/src/content/en/release-notes/9120-91214/menu-improvement-guide-9120.mdx @@ -11,43 +11,43 @@ import { Callout } from 'nextra/components'
-![cover-page.png](/release-notes/9120-91214/menu-improvement-guide-9120/cover-page.png) +cover-page.png
-![1.png](/release-notes/9120-91214/menu-improvement-guide-9120/1.png) +1.png
-![2.png](/release-notes/9120-91214/menu-improvement-guide-9120/2.png) +2.png
-![3.png](/release-notes/9120-91214/menu-improvement-guide-9120/3.png) +3.png
-![4.png](/release-notes/9120-91214/menu-improvement-guide-9120/4.png) +4.png
-![5.png](/release-notes/9120-91214/menu-improvement-guide-9120/5.png) +5.png
-![6.png](/release-notes/9120-91214/menu-improvement-guide-9120/6.png) +6.png
-![7.png](/release-notes/9120-91214/menu-improvement-guide-9120/7.png) +7.png
-![8.png](/release-notes/9120-91214/menu-improvement-guide-9120/8.png) +8.png
-![9.png](/release-notes/9120-91214/menu-improvement-guide-9120/9.png) +9.png
diff --git a/src/content/en/support/premium-support.mdx b/src/content/en/support/premium-support.mdx index d9e13735..cb99410c 100644 --- a/src/content/en/support/premium-support.mdx +++ b/src/content/en/support/premium-support.mdx @@ -13,7 +13,7 @@ Enterprise Edition customers receive fast and structured technical support throu * QueryPie Customer Portal: [Go to Portal](https://help.support.querypie.com/)
-![image-20240801-023748.png](/support/premium-support/image-20240801-023748.png) +image-20240801-023748.png
You can submit tickets for product inquiries, bug reports, and more, and track the progress of your tickets in real-time. diff --git a/src/content/en/user-manual/database-access-control.mdx b/src/content/en/user-manual/database-access-control.mdx index 521fa9ce..3e21e3e4 100644 --- a/src/content/en/user-manual/database-access-control.mdx +++ b/src/content/en/user-manual/database-access-control.mdx @@ -17,7 +17,7 @@ The content displayed in the Privilege item differs depending on how privileges
-![Connection screen when Host Level privilege is assigned](/user-manual/database-access-control/image-20251218-114957.png) +Connection screen when Host Level privilege is assigned
Connection screen when Host Level privilege is assigned
@@ -25,7 +25,7 @@ Connection screen when Host Level privilege is assigned
-![Connection screen when Schema Level privilege is assigned](/user-manual/database-access-control/image-20251218-114753.png) +Connection screen when Schema Level privilege is assigned
Connection screen when Schema Level privilege is assigned
diff --git a/src/content/en/user-manual/database-access-control/connecting-to-custom-data-source.mdx b/src/content/en/user-manual/database-access-control/connecting-to-custom-data-source.mdx index 8c9c4fd0..ac91ac1c 100644 --- a/src/content/en/user-manual/database-access-control/connecting-to-custom-data-source.mdx +++ b/src/content/en/user-manual/database-access-control/connecting-to-custom-data-source.mdx @@ -11,14 +11,14 @@ import { Callout } from 'nextra/components' 1. Navigate to the Workflow menu at the top of the user screen. 2. Click the `Submit Request` button in the top left and select the DB Access Request item.
- ![Screenshot-2025-03-06-at-1.19.24-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-1.19.24-PM.png) + Screenshot-2025-03-06-at-1.19.24-PM.png
3. Set the Approval Rule according to the situation and write the Title. 4. Select an item with Type 'Custom Data Source' from the DB Connection list. 5. Unlike other vendors, Privilege cannot be selected, so it is displayed as "-". 6. Set and write the Expiration Date and Reason for Request items according to the situation.
- ![Screenshot-2025-03-06-at-1.22.28-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-1.22.28-PM.png) + Screenshot-2025-03-06-at-1.22.28-PM.png
7. After completing the writing, click the `Submit` button at the bottom to complete the application. 8. After receiving administrator approval, you can check it in the left Workflow > Sent Request > Done menu. @@ -36,13 +36,13 @@ import { Callout } from 'nextra/components' * Run QueryPie Agent. * You can check Custom Data Source in the Database item.
- ![Screenshot-2025-03-06-at-2.05.26-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.05.26-PM.png) + Screenshot-2025-03-06-at-2.05.26-PM.png
2. **Checking Connection Guide** * When you click on the Custom Data Source connection row in Agent, you can see a row containing Port information. * Right-click on the above row and click Connection Guide to check the connection information.
- ![Screenshot-2025-03-06-at-2.08.11-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.08.11-PM.png) + Screenshot-2025-03-06-at-2.08.11-PM.png
* UID/PW is displayed as unmodifiable db username, db password. * Privileges are displayed as "-". @@ -51,7 +51,7 @@ import { Callout } from 'nextra/components' * **Host and Port must be entered with the information specified in the Connection Guide.** * Enter additional information according to the vendor.
- ![Screenshot-2025-03-06-at-2.18.26-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.18.26-PM.png) + Screenshot-2025-03-06-at-2.18.26-PM.png
@@ -65,11 +65,11 @@ import { Callout } from 'nextra/components' * Click Databases at the top of the user screen. * When you click QueryPie Connections in the left connection list, Custom Data Sources with access permissions are displayed.
- ![Screenshot-2025-03-06-at-2.22.22-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.22.22-PM.png) + Screenshot-2025-03-06-at-2.22.22-PM.png
2. **Connection Not Possible Notice** * When selecting Custom Data Source, the Connect button is disabled. * The following tooltip is displayed and connection via web is not possible:
"Access is only possible through a proxy and cannot be accessed through the web. Please open the QueryPie Agent to connect to the Custom Data Source."
- ![Screenshot-2025-03-06-at-2.23.37-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.23.37-PM.png) + Screenshot-2025-03-06-at-2.23.37-PM.png
diff --git a/src/content/en/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx b/src/content/en/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx index 9caa9338..4f6a279c 100644 --- a/src/content/en/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx +++ b/src/content/en/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx @@ -21,7 +21,7 @@ For setup instructions, please refer to the [Enable Database Proxy](../../overvi
-![QueryPie Web > Data Access Control > Databases > Proxy Info](/user-manual/database-access-control/connecting-to-proxy-without-agent/image-20240731-133408.png) +QueryPie Web > Data Access Control > Databases > Proxy Info
QueryPie Web > Data Access Control > Databases > Proxy Info
@@ -33,7 +33,7 @@ QueryPie Web > Data Access Control > Databases > Proxy Info 4. Click the `Create Token` button at the bottom to issue a user authentication token.
-![QueryPie Web > Data Access Control > Databases > Proxy Info > Create Token](/user-manual/database-access-control/connecting-to-proxy-without-agent/image-20240731-133805.png) +QueryPie Web > Data Access Control > Databases > Proxy Info > Create Token
QueryPie Web > Data Access Control > Databases > Proxy Info > Create Token
diff --git a/src/content/en/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx b/src/content/en/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx index 297b6ddf..bea498e8 100644 --- a/src/content/en/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx +++ b/src/content/en/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx @@ -14,25 +14,25 @@ If your QueryPie administrator has set the authentication method for a BigQuery 1. In the Database section of the QueryPie user page, select the BigQuery connection from the list of connections.
(You will only see connections for which the administrator has granted you access.)
- ![BigQuery connection shown in the connection list in the Database section of the user page](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250226-020846.png) + Reset Token button for BigQuery connection on the user page
BigQuery connection shown in the connection list in the Database section of the user page
2. Click the `Connect` button and select the Google account you will use for sign-in in the popup.
- ![image-20250123-110105.png](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250123-110105.png) + image-20250123-110105.png
3. On the screen explaining sign-in to the service, click Continue.
- ![Sign in to the service](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250123-110419.png) + Sign in to the service
Sign in to the service
4. Allow access to your Google account.
- ![image-20250123-111820.png](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250123-111820.png) + image-20250123-111820.png
5. Wait a moment for the connection to complete. @@ -50,7 +50,7 @@ When you select a BigQuery connection configured for OAuth authentication in the Clicking this button deletes the token stored on the client so you can restart the OAuth authentication flow (signing in to the service with your Google account) from the beginning.
-![Reset Token button for BigQuery connection on the user page](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250226-020846.png) +Reset Token button for BigQuery connection on the user page
Reset Token button for BigQuery connection on the user page
diff --git a/src/content/en/user-manual/database-access-control/connecting-with-web-sql-editor.mdx b/src/content/en/user-manual/database-access-control/connecting-with-web-sql-editor.mdx index 65f5227b..406eb5b5 100644 --- a/src/content/en/user-manual/database-access-control/connecting-with-web-sql-editor.mdx +++ b/src/content/en/user-manual/database-access-control/connecting-with-web-sql-editor.mdx @@ -16,7 +16,7 @@ QueryPie provides a web SQL editor that allows you to execute queries and view d You can check the list of database connections with access permissions granted to individual users or groups, and select the connection to work with to connect to the database.
-![Connection selection and connection screen in User > Databases](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20251218-115500.png) +Connection selection and connection screen in User > Databases
Connection selection and connection screen in User > Databases
@@ -36,7 +36,7 @@ The editor consists of a left object panel, top toolbar, center SQL editor, and #### 1. Top Left Object Panel
-![SQL Editor > Connection Panel](/user-manual/database-access-control/connecting-with-web-sql-editor/screenshot-20240802-141439.png) +SQL Editor > Connection Panel
SQL Editor > Connection Panel
@@ -49,7 +49,7 @@ SQL Editor > Connection Panel #### 2. Left Object Panel
-![SQL Editor > Connection Panel](/user-manual/database-access-control/connecting-with-web-sql-editor/screenshot-20240802-141927.png) +SQL Editor > Connection Panel
SQL Editor > Connection Panel
@@ -64,7 +64,7 @@ SQL Editor > Connection Panel #### 3. Top Toolbar
-![QueryPie Web > Database Access Control > SQL Editor > Toolbar](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240731-115955.png) +QueryPie Web > Database Access Control > SQL Editor > Toolbar
QueryPie Web > Database Access Control > SQL Editor > Toolbar
@@ -89,7 +89,7 @@ QueryPie Web > Database Access Control > SQL Editor > Toolbar
-![SQL Editor > Editor Tab & Result](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-052240.png) +SQL Editor > Editor Tab & Result
SQL Editor > Editor Tab & Result
@@ -103,7 +103,7 @@ SQL Editor > Editor Tab & Result #### 3. Queries Panel
-![SQL Editor > Queries Panel ](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-052539.png) +SQL Editor > Queries Panel
SQL Editor > Queries Panel
@@ -119,7 +119,7 @@ To use this feature, administrators must pre-configure query sharing settings. #### 4. Object Info Panel
-![SQL Editor > Object Info Panel ](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-053427.png) +SQL Editor > Object Info Panel
SQL Editor > Object Info Panel
@@ -136,7 +136,7 @@ SQL Editor > Object Info Panel #### 5. SQL History Panel
-![SQL Editor > SQL History Panel](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-054007.png) +SQL Editor > SQL History Panel
SQL Editor > SQL History Panel
@@ -170,7 +170,7 @@ As shown in the figure below, enter the reason for executing the query in the "W You can enter up to 300 characters.
-![image-20241031-233232.png](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20241031-233232.png) +image-20241031-233232.png
diff --git a/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx b/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx index c1b093d2..6ea12f62 100644 --- a/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx +++ b/src/content/en/user-manual/database-access-control/setting-default-privilege.mdx @@ -14,7 +14,7 @@ This is a feature to set the Default Privilege that connects by default when mul ### Setting Default Privilege
-![QueryPie Web > Database Access Control > Databases > Privileges](/user-manual/database-access-control/setting-default-privilege/image-20240731-124310.png) +QueryPie Web > Database Access Control > Databases > Privileges
QueryPie Web > Database Access Control > Databases > Privileges
@@ -24,7 +24,7 @@ QueryPie Web > Database Access Control > Databases > Privileges 2. When you have been granted 2 or more permissions, users must separately set Default Privilege.
-![QueryPie Web > Database Access Control > Databases > Privileges > Default Privilege Setting](/user-manual/database-access-control/setting-default-privilege/image-20240731-124808.png) +QueryPie Web > Database Access Control > Databases > Privileges > Default Privilege Setting
QueryPie Web > Database Access Control > Databases > Privileges > Default Privilege Setting
diff --git a/src/content/en/user-manual/kubernetes-access-control.mdx b/src/content/en/user-manual/kubernetes-access-control.mdx index de149703..7d9ed0e6 100644 --- a/src/content/en/user-manual/kubernetes-access-control.mdx +++ b/src/content/en/user-manual/kubernetes-access-control.mdx @@ -10,7 +10,7 @@ QueryPie provides functionality to control access permissions to Kubernetes clus You can access clusters with granted permissions through the QueryPie agent, and the KUBECONFIG file required for cluster access is configured through the agent.
-![QueryPie Web > Kubernetes Access Control > Kubernetes](/user-manual/kubernetes-access-control/image-20240724-050502.png) +QueryPie Web > Kubernetes Access Control > Kubernetes
QueryPie Web > Kubernetes Access Control > Kubernetes
diff --git a/src/content/en/user-manual/kubernetes-access-control/checking-access-permission-list.mdx b/src/content/en/user-manual/kubernetes-access-control/checking-access-permission-list.mdx index 174453dd..6b464a8a 100644 --- a/src/content/en/user-manual/kubernetes-access-control/checking-access-permission-list.mdx +++ b/src/content/en/user-manual/kubernetes-access-control/checking-access-permission-list.mdx @@ -15,14 +15,14 @@ Users can view at a glance the list of authorized Kubernetes clusters sorted by Users can check the permissions granted to them in the Kubernetes menu after logging into QueryPie.
-![QueryPie Web > Kubernetes Access Control > Kuber > Select a Role](/user-manual/kubernetes-access-control/checking-access-permission-list/image-20240721-081220.png) +QueryPie Web > Kubernetes Access Control > Kuber > Select a Role
QueryPie Web > Kubernetes Access Control > Kuber > Select a Role
-![QueryPie Web > System Access Control > Kubernetes > Select a Role](/user-manual/kubernetes-access-control/checking-access-permission-list/image-20240723-155143.png) +QueryPie Web > System Access Control > Kubernetes > Select a Role
QueryPie Web > System Access Control > Kubernetes > Select a Role
@@ -36,7 +36,7 @@ QueryPie Web > System Access Control > Kubernetes > Select a Role ### Checking Access Permission List
-![QueryPie Web > System Access Control > Kubernetes ](/user-manual/kubernetes-access-control/checking-access-permission-list/image-20240721-081324.png) +QueryPie Web > System Access Control > Kubernetes
QueryPie Web > System Access Control > Kubernetes
diff --git a/src/content/en/user-manual/multi-agent.mdx b/src/content/en/user-manual/multi-agent.mdx index 290f0a7e..4a6fb5e7 100644 --- a/src/content/en/user-manual/multi-agent.mdx +++ b/src/content/en/user-manual/multi-agent.mdx @@ -38,35 +38,35 @@ Support scope when QueryPie Host version is `10.2.8` or later: 1. After logging into QueryPie, click the profile in the top right corner, then click Download & Support > `Multi-Agent` button.
- ![QueryPie Web > Profile Menu](/user-manual/multi-agent/screenshot-20250217-110358.png) + QueryPie Web > Profile Menu
QueryPie Web > Profile Menu
2. When the QueryPie Multi-Agent Downloads popup appears, download the installation file that matches your PC's operating system in Step 1, then copy the QueryPie URL from Step 3.

- ![QueryPie Web > QueryPie Multi-Agent Download](/user-manual/multi-agent/screenshot-20250413-233322.png) + QueryPie Web > QueryPie Multi-Agent Download
QueryPie Web > QueryPie Multi-Agent Download
3. Run the downloaded QueryPie Multi-Agent installation program and copy the .app file to the Applications folder to complete the installation.
- ![Mac OS Installation Program](/user-manual/multi-agent/screenshot-20250217-105557.png) + Mac OS Installation Program
Mac OS Installation Program
4. When you run the installed QueryPie Agent, the Host initial registration page opens.
Enter the QueryPie URL you copied earlier in the QueryPie Host input field and click the `Next` button to enter the login screen.
- ![Multi-Agent > Host Setting](/user-manual/multi-agent/screenshot-20250217-105917.png) + Multi-Agent > Host Setting
Multi-Agent > Host Setting
5. Enter your authentication information on the login page of the entered host and click the Continue button.
- ![Multi-Agent > Login](/user-manual/multi-agent/screenshot-20250217-110106.png) + Multi-Agent > Login
Multi-Agent > Login
@@ -78,14 +78,14 @@ Support scope when QueryPie Host version is `10.2.8` or later: 1. In the Database tab, you can view the Database Connection list that has been granted permissions and can use Proxy for the selected QueryPie Host.
- ![Multi-Agent > Databases](/user-manual/multi-agent/screenshot-20250307-105512.png) + Multi-Agent > Databases
Multi-Agent > Databases
2. Select the connection you want to connect to and right-click to open the context menu.
- ![Multi-Agent > Databases > Context-menu](/user-manual/multi-agent/screenshot-20250307-105433.png) + Multi-Agent > Databases > Context-menu
Multi-Agent > Databases > Context-menu
@@ -107,7 +107,7 @@ Open Connection With and Copy as JDBC URL features are supported in version 10.2 You can manage 3rd Party tool-related settings in Settings > Databases.
-![Multi-Agent > Settings > Databases](/user-manual/multi-agent/screenshot-20250413-235252.png) +Multi-Agent > Settings > Databases
Multi-Agent > Settings > Databases
@@ -131,28 +131,28 @@ At this time, you can select the Privilege to use when connecting through proxy If a user with multiple privileges does not set a specific privilege as default, they cannot connect, so if no default privilege is set, a warning icon like the one shown below is displayed.
-![image-20250513-025002.png](/user-manual/multi-agent/image-20250513-025002.png) +image-20250513-025002.png
1. Right-click on a connection with multiple Privileges assigned and call the menu. 2. Select Connection Information from the menu.
- ![Connection Information](/user-manual/multi-agent/image-20250513-042753.png) + Connection Information
Connection Information
3. Click the edit (pencil icon) button in the Privilege of Original Information.


- ![image-20250513-043056.png](/user-manual/multi-agent/image-20250513-043056.png) + image-20250513-043056.png
4. Select one of the Privilege Name items and save.
- ![image-20250513-044616.png](/user-manual/multi-agent/image-20250513-044616.png) + image-20250513-044616.png
5. Check that the warning icon disappears and the assigned privilege name is visible for that connection.


- ![image-20250513-045054.png](/user-manual/multi-agent/image-20250513-045054.png) + image-20250513-045054.png
### KAC @@ -162,7 +162,7 @@ If a user with multiple privileges does not set a specific privilege as default, When you select one of the Roles granted to you from the Role selector, you can view the K8s Cluster list that has permissions for the selected Role.
-![Multi-Agent > Kubernetes](/user-manual/multi-agent/screenshot-20250217-113908.png) +Multi-Agent > Kubernetes
Multi-Agent > Kubernetes
@@ -177,7 +177,7 @@ Click the gear button in the top right corner of the agent to enter the Setting Then paste and run the copied command in the terminal you are using.
-![Multi-Agent > Setting > Kubernetes](/user-manual/multi-agent/screenshot-20250217-113712.png) +Multi-Agent > Setting > Kubernetes
Multi-Agent > Setting > Kubernetes
@@ -189,14 +189,14 @@ Multi-Agent > Setting > Kubernetes 1. When you select a Role from the Role dropdown, you can view the server list that can be accessed with the selected Role.
- ![Multi-Agent > Servers](/user-manual/multi-agent/screenshot-20250413-234048.png) + Multi-Agent > Servers
Multi-Agent > Servers
2. Select a server, right-click to open the context menu, and select Open Connection With > Terminal Tool.
- ![Multi-Agent > Servers](/user-manual/multi-agent/screenshot-20250413-234314.png) + Multi-Agent > Servers
Multi-Agent > Servers
@@ -206,7 +206,7 @@ Multi-Agent > Setting > Kubernetes 1. However, when connecting to a Windows Server without Server Agent, only Custom Account can be selected, and the Custom Account input field and Password input field are not displayed. It cannot be used on Windows Servers with Server Agent. 4. You can connect to the server with the selected terminal tool.
- ![screenshot-20250413-234644.png](/user-manual/multi-agent/screenshot-20250413-234644.png) + screenshot-20250413-234644.png
@@ -229,19 +229,19 @@ When you don't have the necessary account permissions to connect to a server, yo 1. Select the server you want to request permission for in the `Servers` tab and right-click to open the context menu.

- ![Screenshot-2025-07-22-at-11.12.13-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.13-AM.png) + Screenshot-2025-07-22-at-11.12.13-AM.png
2. Select the terminal tool you want to use from `Open Connection With`.


- ![Screenshot-2025-07-22-at-11.12.16-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.16-AM.png) + Screenshot-2025-07-22-at-11.12.16-AM.png
3. When the account selection window appears, click the `Request Server Privilege` button at the bottom.


- ![Screenshot-2025-07-22-at-11.12.33-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.33-AM.png) + Screenshot-2025-07-22-at-11.12.33-AM.png
* Clicking this button navigates to the permission request screen on the QueryPie web page, with the previously selected Role, server group, server, and account information automatically filled in.

- ![Screenshot-2025-07-22-at-11.12.49-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.49-AM.png) + Screenshot-2025-07-22-at-11.12.49-AM.png
@@ -253,7 +253,7 @@ When you don't have the necessary account permissions to connect to a server, yo #### Available Filters When Viewing Server List in Agent
-![Multi-Agent > Servers](/user-manual/multi-agent/Screenshot-2025-08-25-at-4.57.03-PM.png) +Multi-Agent > Servers
Multi-Agent > Servers
@@ -267,7 +267,7 @@ Multi-Agent > Servers You can manage terminal tool-related settings in Setting > Servers.
-![Multi-Agent > Setting > Servers](/user-manual/multi-agent/screenshot-20250413-235301.png) +Multi-Agent > Setting > Servers
Multi-Agent > Setting > Servers
@@ -283,7 +283,7 @@ Multi-Agent > Setting > Servers 1. In Settings > Hosts, click the `+ Add New Host` button, enter the domain of the new Host, and save.
- ![Multi-Agent > Setting > General > Add New Host](/user-manual/multi-agent/screenshot-20250413-235030.png) + Multi-Agent > Setting > General > Add New Host
Multi-Agent > Setting > General > Add New Host
@@ -291,14 +291,14 @@ Multi-Agent > Setting > Servers 2. If the new Host registration is successful, you will be notified with a Toast. Check that the new Host has been added to the list and click the `X` button in the top right corner to exit the settings page. 1. You can click on the desired Host in the Host list to switch immediately.
- ![Multi-Agent > Setting > General](/user-manual/multi-agent/screenshot-20250413-235051.png) + Multi-Agent > Setting > General
Multi-Agent > Setting > General
3. Click the profile button to view the registered Host list. You can click to switch between Hosts.
- ![Multi-Agent > Select Profile Menu](/user-manual/multi-agent/screenshot-20250217-114200.png) + Multi-Agent > Select Profile Menu
Multi-Agent > Select Profile Menu
@@ -312,13 +312,13 @@ Host switching is required during login, but after login when Proxy connection i 1. Click the Multi Agent icon (or item) in the system tray or menu bar, then select 'Reset All Settings' from the displayed menu.
-![ Status Bar Item (MacOS)](/user-manual/multi-agent/screenshot-20250414-000719.png) + Status Bar Item (MacOS)
Status Bar Item (MacOS)
-![Application Menu (MacOS)](/user-manual/multi-agent/screenshot-20250414-001207.png) +Application Menu (MacOS)
Application Menu (MacOS)
@@ -326,21 +326,21 @@ Application Menu (MacOS) 1. Or click the gear button in the top right corner of the agent to enter the settings page and click the Reset All Settings button at the bottom of the Hosts tab.
- ![Multi-Agent > Setting > Hosts](/user-manual/multi-agent/screenshot-20250217-114241.png) + Multi-Agent > Setting > Hosts
Multi-Agent > Setting > Hosts
2. Click the Reset button in the confirmation modal to reset all settings stored in the local folder.
- ![Multi-Agent > Setting > Hosts > Reset All Settings](/user-manual/multi-agent/screenshot-20250217-114245.png) + Multi-Agent > Setting > Hosts > Reset All Settings
Multi-Agent > Setting > Hosts > Reset All Settings
3. You will enter the Multi Agent initial setup (initial Host registration) page.
- ![Multi-Agent > Host Setting](/user-manual/multi-agent/screenshot-20250217-114250.png) + Multi-Agent > Host Setting
Multi-Agent > Host Setting
@@ -353,13 +353,13 @@ If problems occur while using Multi-agent, please extract logs following the pro #### GUI
-![MacOS](/user-manual/multi-agent/diagnostic-tools-for-macos.png) +MacOS
MacOS
-![Windows](/user-manual/multi-agent/diagnostic-tools-for-windows.png) +Windows
Windows
diff --git a/src/content/en/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx b/src/content/en/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx index 15977b85..611060a0 100644 --- a/src/content/en/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx +++ b/src/content/en/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx @@ -68,11 +68,11 @@ Download and install AppIndicator and KStatusNotifierItem Support from the link [https://extensions.gnome.org/extension/615/appindicator-support/](https://extensions.gnome.org/extension/615/appindicator-support/)
-![Screenshot-20250404-144620.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/Screenshot-20250404-144620.png) +Screenshot-20250404-144620.png
-![image-20250404-054650.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250404-054650.png) +image-20250404-054650.png
### Debian-based @@ -190,17 +190,17 @@ In the GNOME desktop environment, there is a system that securely stores and man If the **Login keyring is locked** in the Passwords and Keys app, Multi Agent will require administrator privileges at startup.
-![image-20250403-080719.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250403-080719.png) +image-20250403-080719.png
-![image-20250403-080458.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250403-080458.png) +image-20250403-080458.png
If you unlock it using the Unlock button, administrator privileges will not be required at runtime.
-![image-20250403-080814.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250403-080814.png) +image-20250403-080814.png
## Troubleshooting @@ -211,7 +211,7 @@ If a Default Browser is not set, links will not open. Please set a default browser in your browser's settings.
-![image-20250404-100924.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250404-100924.png) +image-20250404-100924.png
diff --git a/src/content/en/user-manual/my-dashboard.mdx b/src/content/en/user-manual/my-dashboard.mdx index 3bc291d5..6d2a2804 100644 --- a/src/content/en/user-manual/my-dashboard.mdx +++ b/src/content/en/user-manual/my-dashboard.mdx @@ -20,7 +20,7 @@ If you access from an IP not allowed by the administrator, the login screen may
-![QueryPie Login Screen](/user-manual/my-dashboard/image-20250725-085352.png) +QueryPie Login Screen
QueryPie Login Screen
@@ -38,7 +38,7 @@ In closed networks where internet communication is not possible, information is You can check QueryPie's user privacy handling policy through the Privacy Policy link.
-![Cookie Settings Screen](/user-manual/my-dashboard/image-20250724-094214.png) +Cookie Settings Screen
Cookie Settings Screen
@@ -58,14 +58,14 @@ As of QueryPie 10.2.2, the provided secondary authentication means are Google OT * Enter the login password on the login page. * Register with the Authenticator app using the QR Code displayed in the popup window during first login. The screen displays guidance text 'Download an authentication app such as Google Authenticator, Microsoft Authenticator, Okta Verify, etc.' to easily select and install a compatible authentication app from the App Store or Google Play Store.
- ![QR Code for Authenticator App Registration](/user-manual/my-dashboard/image-20250808-063052-(2).png) + Authenticator 앱 등록용 QR code
QR Code for Authenticator App Registration
* Enter the one-time authentication code output by the Authenticator app.
- ![Enter One-Time Authentication Code](/user-manual/my-dashboard/image-20241220-021546.png) + Enter One-Time Authentication Code
Enter One-Time Authentication Code
@@ -75,7 +75,7 @@ As of QueryPie 10.2.2, the provided secondary authentication means are Google OT * Check the authentication code in the authentication email received in your inbox.
The authentication code is valid for 30 minutes. * You can request resending of the authentication email through "Resend authentication code". The second resend request is possible after 5 minutes.
- ![Enter One-Time Authentication Code (Email)](/user-manual/my-dashboard/image-20241220-021636.png) + Enter One-Time Authentication Code (Email)
Enter One-Time Authentication Code (Email)
@@ -88,7 +88,7 @@ When login is completed normally, you are redirected to the user dashboard scree The dashboard allows you to view at a glance basic information such as role permissions granted to the currently logged-in user, groups you belong to, approval status, and recently accessed connection lists.
-![My Dashboard](/user-manual/my-dashboard/screenshot-20240801-142503.png) +My Dashboard
My Dashboard
@@ -121,7 +121,7 @@ Only users assigned the QueryPie administrator role can see the `Go to Admin Pag Clicking this button opens the administrator page in a separate tab.
-![My Dashboard > Top Right Menu](/user-manual/my-dashboard/screenshot-20240801-145006.png) +My Dashboard > Top Right Menu
My Dashboard > Top Right Menu
diff --git a/src/content/en/user-manual/my-dashboard/user-password-reset-via-email.mdx b/src/content/en/user-manual/my-dashboard/user-password-reset-via-email.mdx index d5783d07..35d5d1cb 100644 --- a/src/content/en/user-manual/my-dashboard/user-password-reset-via-email.mdx +++ b/src/content/en/user-manual/my-dashboard/user-password-reset-via-email.mdx @@ -24,7 +24,7 @@ If you have been notified by an administrator about user password reset, you sho The content of the email that users receive is similar to the following.
-![Password Reset Email](/user-manual/my-dashboard/user-password-reset-via-email/image-20241218-224655.png) +Password Reset Email
Password Reset Email
@@ -37,41 +37,41 @@ In this case, you must request password reset from the administrator again. 1. Click the "Forgot your password?" link on the login page.
- ![Forgot your password?](/user-manual/my-dashboard/user-password-reset-via-email/image-20241218-233331.png) + Forgot your password?
Forgot your password?
2. Enter your ID in the dialog box and click the `Request` button.

- ![Password Reset Request](/user-manual/my-dashboard/user-password-reset-via-email/image-20241220-030541.png) + Password Reset Request
Password Reset Request
3. Check if an authentication code for identity verification has been received in your inbox.

- ![Authentication Code Received via Email](/user-manual/my-dashboard/user-password-reset-via-email/image-20241218-234314.png) + Authentication Code Received via Email
Authentication Code Received via Email
4. Enter the authentication code confirmed in the email. The received authentication code must be entered within 30 minutes. If you didn't receive the email, you can click the "Resend authentication code" link to request the authentication code email again. However, resend requests are only possible 5 minutes after the initial resend.

- ![Enter Authentication Code](/user-manual/my-dashboard/user-password-reset-via-email/image-20241220-030233.png) + Enter Authentication Code
Enter Authentication Code
5. Enter your ID and register a new password.


- ![Enter New Password](/user-manual/my-dashboard/user-password-reset-via-email/image-20241219-002622.png) + Enter New Password
Enter New Password
- ![Confirm Password Change](/user-manual/my-dashboard/user-password-reset-via-email/image-20241219-000927.png) + Confirm Password Change
Confirm Password Change
diff --git a/src/content/en/user-manual/preferences.mdx b/src/content/en/user-manual/preferences.mdx index 3facde8f..7fde831c 100644 --- a/src/content/en/user-manual/preferences.mdx +++ b/src/content/en/user-manual/preferences.mdx @@ -15,7 +15,7 @@ Use the Preferences page to configure your personal settings in QueryPie. To configure your personal settings, click your user account at the top-right of the menu bar and select Preferences.
-![image-20250724-092314.png](/user-manual/preferences/image-20250724-092314.png) +image-20250724-092314.png
@@ -29,7 +29,7 @@ If you use SSO Login, please use your IdP's user settings to change your passwor
-![Top menu bar > Profile > Preferences > My Account](/user-manual/preferences/image-20250725-050431.png) +Top menu bar > Profile > Preferences > My Account
Top menu bar > Profile > Preferences > My Account
@@ -56,7 +56,7 @@ For detailed instructions on proxy approval, see [Additional Approval Features (
-![Top menu bar > Profile > Preferences > Approver Settings](/user-manual/preferences/image-20250725-050830.png) +Top menu bar > Profile > Preferences > Approver Settings
Top menu bar > Profile > Preferences > Approver Settings
@@ -73,7 +73,7 @@ Top menu bar > Profile > Preferences > Approver Settings Use the Editor tab to configure the display and behavior of the SQL editor.
-![Top menu bar > Profile > Preferences > Editor](/user-manual/preferences/image-20250725-051417.png) +Top menu bar > Profile > Preferences > Editor
Top menu bar > Profile > Preferences > Editor
@@ -98,7 +98,7 @@ Top menu bar > Profile > Preferences > Editor Use the Shortcut tab to view and edit keyboard shortcuts used in the SQL Editor (double-click to edit).
-![Top menu bar > Profile > Preferences > Shortcut](/user-manual/preferences/image-20250725-052245.png) +Top menu bar > Profile > Preferences > Shortcut
Top menu bar > Profile > Preferences > Shortcut
@@ -110,7 +110,7 @@ Top menu bar > Profile > Preferences > Shortcut Use the Configuration tab to manage Kerberos keytabs. Click `Create Keytab` to upload a keytab file.
-![Top menu bar > Profile > Preferences > Configuration](/user-manual/preferences/image-20250725-052630.png) +Top menu bar > Profile > Preferences > Configuration
Top menu bar > Profile > Preferences > Configuration
@@ -122,7 +122,7 @@ Top menu bar > Profile > Preferences > Configuration In the Terminal tab, configure the font size (default 12, min 9, max 24) and color theme used for text-based connections such as SSH.
-![Top menu bar > Profile > Preferences > Terminal](/user-manual/preferences/image-20250725-053323.png) +Top menu bar > Profile > Preferences > Terminal
Top menu bar > Profile > Preferences > Terminal
@@ -136,7 +136,7 @@ On closed networks without internet connectivity, no cookie information is trans The Privacy Policy pages are available when the internet-accessible QueryPie website is reachable.
[https://www.querypie.com/privacy-policy](https://www.querypie.com/privacy-policy) (English)
[https://www.querypie.com/ko/privacy-policy](https://www.querypie.com/ko/privacy-policy) (Korean)
[https://www.querypie.com/ja/privacy-policy](https://www.querypie.com/ja/privacy-policy) (Japanese)
-![Top menu bar > Profile > Preferences > Terminal](/user-manual/preferences/image-20250725-053955.png) +Top menu bar > Profile > Preferences > Terminal
Top menu bar > Profile > Preferences > Terminal
@@ -152,7 +152,7 @@ Experimental features may be less stable and may be removed in future versions.
-![Top menu bar > Profile > Preferences > QueryPie Lab](/user-manual/preferences/image-20250725-054439.png) +Top menu bar > Profile > Preferences > QueryPie Lab
Top menu bar > Profile > Preferences > QueryPie Lab
diff --git a/src/content/en/user-manual/server-access-control.mdx b/src/content/en/user-manual/server-access-control.mdx index b25fd1e0..284d0428 100644 --- a/src/content/en/user-manual/server-access-control.mdx +++ b/src/content/en/user-manual/server-access-control.mdx @@ -11,7 +11,7 @@ Users who have been granted access permissions for connections can connect to co Access permissions can be granted to individual users or user groups.
-![QueryPie Web > Server Access Control > Servers](/user-manual/server-access-control/image-20240724-050800.png) +QueryPie Web > Server Access Control > Servers
QueryPie Web > Server Access Control > Servers
diff --git a/src/content/en/user-manual/server-access-control/connecting-to-authorized-servers.mdx b/src/content/en/user-manual/server-access-control/connecting-to-authorized-servers.mdx index f0c4f7a5..c8da5adf 100644 --- a/src/content/en/user-manual/server-access-control/connecting-to-authorized-servers.mdx +++ b/src/content/en/user-manual/server-access-control/connecting-to-authorized-servers.mdx @@ -15,7 +15,7 @@ After selecting a server to connect to, users can execute commands and perform t ### Selecting Role
-![QueryPie Web > System Access Control > Servers > Select a Role](/user-manual/server-access-control/connecting-to-authorized-servers/image-20240723-155143.png) +QueryPie Web > System Access Control > Servers > Select a Role
QueryPie Web > System Access Control > Servers > Select a Role
@@ -28,7 +28,7 @@ QueryPie Web > System Access Control > Servers > Select a Role ### Connecting to Server
-![QueryPie Web > System Access Control > Servers](/user-manual/server-access-control/connecting-to-authorized-servers/Screenshot-2025-08-25-at-4.46.51-PM.png) +QueryPie Web > System Access Control > Servers
QueryPie Web > System Access Control > Servers
@@ -73,7 +73,7 @@ After installing the QueryPie Agent (User Agent / Multi-Agent), right-click the From version 11.3.0, in Multi-Agent, you can select a Custom Account and manually enter the account password to connect.
-![image-20251010-095324.png](/user-manual/server-access-control/connecting-to-authorized-servers/image-20251010-095324.png) +image-20251010-095324.png
diff --git a/src/content/en/user-manual/server-access-control/using-web-sftp.mdx b/src/content/en/user-manual/server-access-control/using-web-sftp.mdx index 85b114a1..93816fb9 100644 --- a/src/content/en/user-manual/server-access-control/using-web-sftp.mdx +++ b/src/content/en/user-manual/server-access-control/using-web-sftp.mdx @@ -14,7 +14,7 @@ QueryPie provides web SFTP that allows you to perform various tasks through a we ### Web SFTP Screen Layout
-![QueryPie Web > Servers > Terminal](/user-manual/server-access-control/using-web-sftp/image-20240802-061021.png) +QueryPie Web > Servers > Terminal
QueryPie Web > Servers > Terminal
@@ -27,7 +27,7 @@ QueryPie Web > Servers > Terminal ### Using Web SFTP Features
-![image-20240723-160917.png](/user-manual/server-access-control/using-web-sftp/image-20240723-160917.png) +image-20240723-160917.png
1. Path display window: Shows the current location, and you can easily navigate by entering the desired path and pressing the `Enter` button. @@ -46,7 +46,7 @@ Some features may be restricted depending on the policies set by the administrat You can check the transfer status and results through the following popup window when uploading and downloading files.
-![image-20240802-061430.png](/user-manual/server-access-control/using-web-sftp/image-20240802-061430.png) +image-20240802-061430.png
1. **Name** : The names of directories and files are displayed. diff --git a/src/content/en/user-manual/server-access-control/using-web-terminal.mdx b/src/content/en/user-manual/server-access-control/using-web-terminal.mdx index 63f1b4cd..38e4320b 100644 --- a/src/content/en/user-manual/server-access-control/using-web-terminal.mdx +++ b/src/content/en/user-manual/server-access-control/using-web-terminal.mdx @@ -14,7 +14,7 @@ QueryPie provides a web terminal that allows you to execute commands through a w ### Web Terminal Screen Layout
-![QueryPie Web > Servers > Terminal](/user-manual/server-access-control/using-web-terminal/image-20240802-060417.png) +QueryPie Web > Servers > Terminal
QueryPie Web > Servers > Terminal
@@ -33,7 +33,7 @@ If you want to use it, please set the User High Performance Web Terminal switch ### Connecting Multiple Servers
-![QueryPie Web > Servers > Terminal](/user-manual/server-access-control/using-web-terminal/image-20240723-160622.png) +QueryPie Web > Servers > Terminal
QueryPie Web > Servers > Terminal
@@ -47,7 +47,7 @@ QueryPie Web > Servers > Terminal ### Opening Multiple Sessions
-![Servers > Terminal > Open New Session](/user-manual/server-access-control/using-web-terminal/image-20240723-160649.png) +Servers > Terminal > Open New Session
Servers > Terminal > Open New Session
diff --git a/src/content/en/user-manual/user-agent.mdx b/src/content/en/user-manual/user-agent.mdx index ffa0282a..0ec8c2b6 100644 --- a/src/content/en/user-manual/user-agent.mdx +++ b/src/content/en/user-manual/user-agent.mdx @@ -16,7 +16,7 @@ By installing QueryPie Agent, you can use SQL Clients like DataGrip and DBeaver, 1. After logging into QueryPie, click the profile in the top right and click the `Agent Download` button.
-![QueryPie Web > Profile Menu](/user-manual/user-agent/screenshot-20240804-173002.png) +QueryPie Web > Profile Menu
QueryPie Web > Profile Menu
@@ -25,7 +25,7 @@ QueryPie Web > Profile Menu 2. When the QueryPie Agent Downloads popup window opens, download the installation file that matches your PC's operating system in Step 1, then copy the QueryPie URL in Step 3.
-![QueryPie Web > Agent Downloads Popup Window](/user-manual/user-agent/image-20240723-154847.png) +QueryPie Web > Agent Downloads Popup Window
QueryPie Web > Agent Downloads Popup Window
@@ -38,7 +38,7 @@ QueryPie Agent supports Mac, Windows, and Linux OS. 3. Run the downloaded QueryPie Agent installer to complete the installation.
-![Mac OS Installer](/user-manual/user-agent/screenshot-20240804-174002.png) +Mac OS Installer
Mac OS Installer
@@ -48,7 +48,7 @@ Mac OS Installer Enter the previously copied QueryPie URL in the QueryPie Host input field and click the `Next` button to enter the login screen.
-![Agent > QueryPie Host Input](/user-manual/user-agent/agent-03.png) +Agent > QueryPie Host Input
Agent > QueryPie Host Input
@@ -60,13 +60,13 @@ Agent > QueryPie Host Input 1. Click the `Login` button on the login screen within the Agent app.
-![screenshot-20240804-173713.png](/user-manual/user-agent/screenshot-20240804-173713.png) +screenshot-20240804-173713.png
2. When the web browser opens, enter your authentication information on the login page and click the `Continue` button.
-![QueryPie Web > Agent Login Page](/user-manual/user-agent/screenshot-20240729-171236.png) +QueryPie Web > Agent Login Page
QueryPie Web > Agent Login Page
@@ -75,7 +75,7 @@ QueryPie Web > Agent Login Page 3. Upon successful login, the login success screen is displayed as shown below, and then you return to the Agent.
-![QueryPie Web > Agent Login Success Page](/user-manual/user-agent/screenshot-20240729-171314.png) +QueryPie Web > Agent Login Success Page
QueryPie Web > Agent Login Success Page
@@ -84,7 +84,7 @@ QueryPie Web > Agent Login Success Page 4. Explicitly perform Agent opening to transfer authentication information to the Agent.
-![Chrome - Agent App Open Modal](/user-manual/user-agent/screenshot-20240804-174209.png) +Chrome - Agent App Open Modal
Chrome - Agent App Open Modal
@@ -95,7 +95,7 @@ Chrome - Agent App Open Modal 1. After login is completed normally, you can check the connection information for authorized connections in the Databases tab within the Agent app.
Click the `Port` assigned to the connection you want to connect to, and you can check the `Proxy Credentials` information for that connection.
-![Agent > DB Connection Information](/user-manual/user-agent/screenshot-20240730-151001.png) +Agent > DB Connection Information
Agent > DB Connection Information
@@ -104,7 +104,7 @@ Agent > DB Connection Information 2. Enter the above connection information into a 3rd party client to connect to the DB connection.
-![DB Connection Access Using 3rd Party Client](/user-manual/user-agent/agent-07.png) +DB Connection Access Using 3rd Party Client
DB Connection Access Using 3rd Party Client
@@ -121,7 +121,7 @@ After login is completed normally, you can check authorized servers in the Serve * When selecting the Default role, use the server permissions assigned through Workflow > Server Access Request.
-![Agent > Server > Select a Role](/user-manual/user-agent/screenshot-20240730-162653.png) +Agent > Server > Select a Role
Agent > Server > Select a Role
@@ -136,7 +136,7 @@ If you have two or more roles, you must complete role selection first before usi * Right-click on the server you want to connect to and select the Open Connection with menu to choose the terminal tool you want to use.
-![Agent > Server > Open Connection with](/user-manual/user-agent/screenshot-20240730-161729.png) +Agent > Server > Open Connection with
Agent > Server > Open Connection with
@@ -146,7 +146,7 @@ Agent > Server > Open Connection with * Select the account you want to use, enter the password if necessary, then click the `OK` button to open the session.
-![Agent > Server > Open New Session](/user-manual/user-agent/screenshot-20240730-162532.png) +Agent > Server > Open New Session
Agent > Server > Open New Session
@@ -194,7 +194,7 @@ $ ssh deploy@{{Server Name}} ### Kubernetes Access through Agent
-![kubernetes-agent-access-flow.png](/user-manual/user-agent/kubernetes-agent-access-flow.png) +kubernetes-agent-access-flow.png
* Authorized users automatically receive a `kubeconfig` file according to current policies when running the agent. @@ -208,7 +208,7 @@ Click the `Role` button below the user profile area to open the role selection m Choose the desired role and click the `OK` button.
-![Agent > Kubernetes > Select a Role](/user-manual/user-agent/screenshot-20240730-152705.png) +Agent > Kubernetes > Select a Role
Agent > Kubernetes > Select a Role
@@ -225,7 +225,7 @@ Resources accessible according to the selected role are displayed. Click the `🔍` button on the right of each cluster to display the Policy Information popup window where you can check the detailed list of policies applied to that cluster.
-![Agent > Policy Information](/user-manual/user-agent/screenshot-20240730-161141.png) +Agent > Policy Information
Agent > Policy Information
@@ -236,7 +236,7 @@ Agent > Policy Information Click the `KubeConfig Path` button in the Agent settings menu to open the Kubeconfig path configuration modal.
-![Agent > Settings > Configure Kubeconfig Path](/user-manual/user-agent/screenshot-20240730-154623.png) +Agent > Settings > Configure Kubeconfig Path
Agent > Settings > Configure Kubeconfig Path
@@ -248,7 +248,7 @@ Agent > Settings > Configure Kubeconfig Path
-![Path Selection Popup](/user-manual/user-agent/screenshot-20240730-163530.png) +Path Selection Popup
Path Selection Popup
@@ -287,7 +287,7 @@ Resetting settings will initialize the QueryPie Host information you entered, al Click the `⚙️` button on the right of the profile area to open the settings menu. Click the `Reset All Settings` button.
-![Agent > Settings](/user-manual/user-agent/screenshot-20240730-153518.png) +Agent > Settings
Agent > Settings
@@ -299,7 +299,7 @@ Agent > Settings Click the QueryPie Agent icon in the menu bar to open the app menu. Click the `Reset All Settings` button.
-![Agent > App menu](/user-manual/user-agent/screenshot-20240730-153524.png) +Agent > App menu
Agent > App menu
diff --git a/src/content/en/user-manual/web-access-control.mdx b/src/content/en/user-manual/web-access-control.mdx index 669d9b46..b6c57042 100644 --- a/src/content/en/user-manual/web-access-control.mdx +++ b/src/content/en/user-manual/web-access-control.mdx @@ -11,7 +11,7 @@ It enhances security by applying role-based access control (RBAC) to all web app It provides complete visibility by tracking and recording all user web activities in real-time.
-![QueryPie Web > Web Access Control > Web Apps](/user-manual/web-access-control/image-20250629-151148.png) +QueryPie Web > Web Access Control > Web Apps
QueryPie Web > Web Access Control > Web Apps
diff --git a/src/content/en/user-manual/web-access-control/accessing-web-applications-websites.mdx b/src/content/en/user-manual/web-access-control/accessing-web-applications-websites.mdx index b38732be..08b66ad2 100644 --- a/src/content/en/user-manual/web-access-control/accessing-web-applications-websites.mdx +++ b/src/content/en/user-manual/web-access-control/accessing-web-applications-websites.mdx @@ -13,7 +13,7 @@ Select an appropriate Role or, if you don't have a Role, request permission to a ### Selecting a Role
-![QueryPie Web > Web Access Control > Web Apps > Select a Role](/user-manual/web-access-control/accessing-web-applications-websites/image-20250629-151725.png) +QueryPie Web > Web Access Control > Web Apps > Select a Role
QueryPie Web > Web Access Control > Web Apps > Select a Role
@@ -26,7 +26,7 @@ QueryPie Web > Web Access Control > Web Apps > Select a Role ### Accessing Web Applications (Websites)
-![QueryPie Web > Web Access Control > Web Apps](/user-manual/web-access-control/accessing-web-applications-websites/image-20250629-152117.png) +QueryPie Web > Web Access Control > Web Apps
QueryPie Web > Web Access Control > Web Apps
diff --git a/src/content/en/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx b/src/content/en/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx index d2782946..82505e56 100644 --- a/src/content/en/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx +++ b/src/content/en/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx @@ -18,7 +18,7 @@ This page guides you through the process of installing the Root CA certificate a 1. While logged into QueryPie, click the profile icon in the top right, then navigate to Support > Download Web Secure menu.
-![QueryPie > Profile Menu](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20241223-120321.png) +QueryPie > Profile Menu
QueryPie > Profile Menu
@@ -27,7 +27,7 @@ QueryPie > Profile Menu 1. When the QueryPie Web Secure Download modal window appears, click the Step 1. Download Link in the A. Install Root CA Certificate section as shown in the picture below to download the certificate file.
-![QueryPie Web Secure Download](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20250116-155957.png) +QueryPie Web Secure Download
QueryPie Web Secure Download
@@ -46,7 +46,7 @@ QueryPie Web Secure Download * Drag and drop the downloaded Extension file (without extracting) into the extensions page.
-![Chrome > Extension Management](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20241219-192626.png) +Chrome > Extension Management
Chrome > Extension Management
@@ -58,7 +58,7 @@ Chrome > Extension Management * If the Host information is valid, the `Go to Dashboard` button becomes active. Click this button to navigate to the QueryPie dashboard in a new tab.
-![Host Configuration page](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20241219-192931.png) +Host Configuration page
Host Configuration page
diff --git a/src/content/en/user-manual/workflow.mdx b/src/content/en/user-manual/workflow.mdx index 33f4c558..9a7f0ff3 100644 --- a/src/content/en/user-manual/workflow.mdx +++ b/src/content/en/user-manual/workflow.mdx @@ -16,13 +16,13 @@ You can conveniently proceed with request, approval, and execution tasks in an i QueryPie provides two paths to enter the Workflow menu.
-![Top Menu > General > Workflow](/user-manual/workflow/screenshot-20240902-172212.png) +Top Menu > General > Workflow
Top Menu > General > Workflow
-![My Dashboard > Workflow Requests](/user-manual/workflow/screenshot-20240725-145441.png) +My Dashboard > Workflow Requests
My Dashboard > Workflow Requests
@@ -88,7 +88,7 @@ For detailed information about proxy approval, you can find more details in the 2. Click on the request you want to process to check the details, then click `Approve` or `Reject` in the top right.
-![Workflow > Received Requests > To Do > List Details](/user-manual/workflow/image-20240801-062129.png) +Workflow > Received Requests > To Do > List Details
Workflow > Received Requests > To Do > List Details
@@ -111,7 +111,7 @@ There are lists for items to be executed (To Do) and completed items (Done), and #### Executing SQL Request
-![Workflow > Executions > To Do > List Details](/user-manual/workflow/screenshot-20240725-094850.png) +Workflow > Executions > To Do > List Details
Workflow > Executions > To Do > List Details
@@ -135,7 +135,7 @@ This background query execution feature is only supported in QueryPie v9.15.0 an #### Executing SQL Export Request
-![Workflow > Executions > To Do](/user-manual/workflow/screenshot-20240725-104719.png) +Workflow > Executions > To Do
Workflow > Executions > To Do
diff --git a/src/content/en/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx b/src/content/en/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx index cb68f667..d292ac97 100644 --- a/src/content/en/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx +++ b/src/content/en/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx @@ -14,7 +14,7 @@ This page introduces additional features that add convenience when using Workflo ### Processing Referenced Request Confirmations
-![Workflow > Reviews > All Reviews > Review Details](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-114129.png) +Workflow > Reviews > All Reviews > Review Details
Workflow > Reviews > All Reviews > Review Details
@@ -37,7 +37,7 @@ The usage method is as follows: #### 1. Setting Up Proxy Approval
-![User > Click Profile in Top Menu Bar > Preferences](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-120401.png) +User > Click Profile in Top Menu Bar > Preferences
User > Click Profile in Top Menu Bar > Preferences
@@ -53,13 +53,13 @@ User > Click Profile in Top Menu Bar > Preferences During the proxy approval setting period, the following is displayed in the top menu bar when the original approver and proxy approver access:
-![Display content based on original approver](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-120741.png) +Display content based on original approver
Display content based on original approver
-![Display content based on proxy approver](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-120854.png) +Display content based on proxy approver
Display content based on proxy approver
@@ -77,7 +77,7 @@ The requester can select Approval Rule and Approver as usual. * You can approve or reject on the detail page, and when entering comments, a message indicating that you are in proxy approval is displayed.
-![screenshot-20240802-124638.png](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-124638.png) +screenshot-20240802-124638.png
#### 4. Checking Requests Processed by Proxy Approval @@ -85,14 +85,14 @@ The requester can select Approval Rule and Approver as usual. * You can check whether the request was processed by the original approver or proxy approver in the approval status within the request detail page as follows: **When processed by the original approver**
-![No proxy approval related text](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240725-153533.png) +No proxy approval related text
No proxy approval related text
**When processed by the proxy approver**
-![Proxy approver is displayed with Done by the delegate](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240725-152141.png) +Proxy approver is displayed with Done by the delegate
Proxy approver is displayed with Done by the delegate
@@ -112,7 +112,7 @@ For detailed information about Slack DM notifications, please refer to the [Usin You can resubmit approval requests with the same content repeatedly or for rejected approval items as follows:
-![Workflow > Sent Requests > Done > List Details](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/image-20230824-110815.png) +Workflow > Sent Requests > Done > List Details
Workflow > Sent Requests > Done > List Details
diff --git a/src/content/en/user-manual/workflow/requesting-access-role.mdx b/src/content/en/user-manual/workflow/requesting-access-role.mdx index 70b23adf..5d5b05cb 100644 --- a/src/content/en/user-manual/workflow/requesting-access-role.mdx +++ b/src/content/en/user-manual/workflow/requesting-access-role.mdx @@ -22,7 +22,7 @@ Roles are granted immediately upon approval, and you can access servers or Kuber * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-access-role/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. Assigning Approvers @@ -34,7 +34,7 @@ Roles are granted immediately upon approval, and you can access servers or Kuber * **All Assignees must approve this request**: All approvers must approve for the approval request to be approved.
-![image-20240807-130021.png](/user-manual/workflow/requesting-access-role/image-20240807-130021.png) +image-20240807-130021.png
#### 3. Assigning Reviewers @@ -45,7 +45,7 @@ Roles are granted immediately upon approval, and you can access servers or Kuber * Close the modal by clicking the `Save` button to complete reviewer assignment.
-![image-20240807-130031.png](/user-manual/workflow/requesting-access-role/image-20240807-130031.png) +image-20240807-130031.png
#### 4. Sending Request with Post-Approval @@ -54,7 +54,7 @@ Roles are granted immediately upon approval, and you can access servers or Kuber * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![image-20240807-130043.png](/user-manual/workflow/requesting-access-role/image-20240807-130043.png) +image-20240807-130043.png
@@ -65,7 +65,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent #### 5. Selecting Target Role
-![QueryPie Web > Workflow > Submit Request > Access Role Request > Step 2](/user-manual/workflow/requesting-access-role/screenshot-20240802-111018.png) +QueryPie Web > Workflow > Submit Request > Access Role Request > Step 2
QueryPie Web > Workflow > Submit Request > Access Role Request > Step 2
@@ -83,7 +83,7 @@ Since separate approval requests are required for each role, permission manageme
-![Screenshot-2025-08-26-at-1.18.14-AM.png](/user-manual/workflow/requesting-access-role/Screenshot-2025-08-26-at-1.18.14-AM.png) +Screenshot-2025-08-26-at-1.18.14-AM.png
1. **Role Expiration Date**: Select the expiration date when the permission will be revoked. @@ -93,7 +93,7 @@ Since separate approval requests are required for each role, permission manageme #### 6. Entering Request Information
-![QueryPie Web > Workflow > Submit Request > Access Role Request > Step 3](/user-manual/workflow/requesting-access-role/Screenshot-2025-08-26-at-1.09.31-AM.png) +QueryPie Web > Workflow > Submit Request > Access Role Request > Step 3
QueryPie Web > Workflow > Submit Request > Access Role Request > Step 3
diff --git a/src/content/en/user-manual/workflow/requesting-db-access.mdx b/src/content/en/user-manual/workflow/requesting-db-access.mdx index 1f3e61d2..0d0bf98f 100644 --- a/src/content/en/user-manual/workflow/requesting-db-access.mdx +++ b/src/content/en/user-manual/workflow/requesting-db-access.mdx @@ -22,7 +22,7 @@ After approval is completed, permissions are immediately granted, and you can ac * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.21.07-AM.png](/user-manual/workflow/requesting-db-access/Screenshot-2025-08-26-at-12.21.07-AM.png) +Screenshot-2025-08-26-at-12.21.07-AM.png
#### 2. Assigning Approvers @@ -34,7 +34,7 @@ After approval is completed, permissions are immediately granted, and you can ac * All Assignees must approve this request: All approvers must approve for the approval request to be approved.
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-db-access/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. Assigning Reviewers @@ -45,7 +45,7 @@ After approval is completed, permissions are immediately granted, and you can ac * Close the modal by clicking the `Save` button to complete reviewer assignment.
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-db-access/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. Sending Request with Post-Approval @@ -58,7 +58,7 @@ From version 11.3.0, when sending a request in post-approval mode, you can no lo * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-db-access/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -73,7 +73,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent * **Reason for Request** : Enter the reason for requesting access permission.
-![User > Workflow > Submit Request > DB Access Request > Request Summary](/user-manual/workflow/requesting-db-access/Screenshot-2025-08-26-at-12.24.44-AM.png) +User > Workflow > Submit Request > DB Access Request > Request Summary
User > Workflow > Submit Request > DB Access Request > Request Summary
@@ -87,13 +87,13 @@ User > Workflow > Submit Request > DB Access Request > Request Summa * **Expiration Date** : Displays the expiration date of the permissions currently granted for that connection. * Select the DB connections for which you want to request access permissions using checkboxes, then you can select the Privilege Type using the following two methods:
-![Specifying per connection through dropdown](/user-manual/workflow/requesting-db-access/screenshot-20240801-191054.png) +Specifying per connection through dropdown
Specifying per connection through dropdown
-![Bulk application through checkboxes and Apply button](/user-manual/workflow/requesting-db-access/screenshot-20240801-191152.png) +Bulk application through checkboxes and Apply button
Bulk application through checkboxes and Apply button
@@ -113,33 +113,33 @@ The following content omits common parts and focuses on the different parts. 1. Click the Submit Request button and select "DB Access Request (Schema Level)" from the menu.
- ![image-20251218-120432.png](/user-manual/workflow/requesting-db-access/image-20251218-120432.png) + image-20251218-120432.png
2. Click the `Add Item` button.
- ![image-20251218-120721.png](/user-manual/workflow/requesting-db-access/image-20251218-120721.png) + image-20251218-120721.png
3. Select the connection to connect to from the left panel.
- ![image-20251218-121011.png](/user-manual/workflow/requesting-db-access/image-20251218-121011.png) + image-20251218-121011.png
4. When you select a connection, you can see that SELECT privilege is automatically granted to schemas that require select privilege in the privilege item on the right. You can remove this item, but if you do, errors may occur when querying schema structure in Web editor or proxy, so do not remove this item unless necessary.
Click the `Add Item` button.
- ![image-20251218-121402.png](/user-manual/workflow/requesting-db-access/image-20251218-121402.png) + image-20251218-121402.png
5. A row is added below where you can add targets. For DBMS with schema structure (Oracle, Postgres, etc.), you must enter the target name in the format `{database name}`.`{schema name}`. For DBMS without schema structure like MySQL, enter only the logical DB name.
- ![image-20251218-122027.png](/user-manual/workflow/requesting-db-access/image-20251218-122027.png) + image-20251218-122027.png
* Oracle example: ORCLDB.TESTUSER * PostgreSQL example: testdb.test_schema * MySQL example: sakila
6. To assign privileges, first select the desired privilege type from the Host Level Privilege item at the top right of the popup window. (Schema level privileges can only be granted within the scope of host level privileges. For example, if you select Read/Write as Host Level Privilege, you can grant SELECT, INSERT, etc. within that scope, but if you select Read-Only as Host Level Privilege, you can only specify SELECT.) If there are no privileges needed for Host Level privilege assignment, you must request the administrator to create a privilege type with specific privileges for that connection.
- ![image-20251218-122450.png](/user-manual/workflow/requesting-db-access/image-20251218-122450.png) + image-20251218-122450.png
7. Host Level Others and Host Level Functions displayed below are read-only. They are used to check upper-level information because Schema Level privileges are dependent on the properties of Host Level Privileges.
- ![image-20251218-122702.png](/user-manual/workflow/requesting-db-access/image-20251218-122702.png) + image-20251218-122702.png
8. Click the `OK` button, enter the remaining parts of the form, and click the `Submit` button to complete the request. diff --git a/src/content/en/user-manual/workflow/requesting-db-policy-exception.mdx b/src/content/en/user-manual/workflow/requesting-db-policy-exception.mdx index 93055cf5..9838bb19 100644 --- a/src/content/en/user-manual/workflow/requesting-db-policy-exception.mdx +++ b/src/content/en/user-manual/workflow/requesting-db-policy-exception.mdx @@ -21,7 +21,7 @@ That is, when the new policy feature is activated, use the DB Policy Exception R * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-db-policy-exception/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. Assigning Approvers @@ -33,7 +33,7 @@ That is, when the new policy feature is activated, use the DB Policy Exception R * All Assignees must approve this request: All approvers must approve for the approval request to be approved.
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-db-policy-exception/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. Assigning Reviewers @@ -44,7 +44,7 @@ That is, when the new policy feature is activated, use the DB Policy Exception R * Close the modal by clicking the `Save` button to complete reviewer assignment.
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-db-policy-exception/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. Sending Request with Post-Approval @@ -53,7 +53,7 @@ That is, when the new policy feature is activated, use the DB Policy Exception R * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-db-policy-exception/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -80,7 +80,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent * Click the `Submit` button at the bottom of the page to submit the request.
-![User > Workflow > Submit Request > DB Policy Exception Request](/user-manual/workflow/requesting-db-policy-exception/image-20251009-144630.png) +User > Workflow > Submit Request > DB Policy Exception Request
User > Workflow > Submit Request > DB Policy Exception Request
diff --git a/src/content/en/user-manual/workflow/requesting-ip-registration.mdx b/src/content/en/user-manual/workflow/requesting-ip-registration.mdx index abc8a3c6..846907cb 100644 --- a/src/content/en/user-manual/workflow/requesting-ip-registration.mdx +++ b/src/content/en/user-manual/workflow/requesting-ip-registration.mdx @@ -21,7 +21,7 @@ After approval is completed, system access from that IP is immediately allowed. * **Approval Expiration Date** : Enter the approval expiration date. The maximum value can be set through Maximum Approval Duration.
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. Assigning Approvers @@ -33,7 +33,7 @@ After approval is completed, system access from that IP is immediately allowed. * **All Assignees must approve this request** : All approvers must approve for the approval request to be approved.
-![Screenshot-2025-06-26-at-3.56.29-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-3.56.29-PM.png) +Screenshot-2025-06-26-at-3.56.29-PM.png
#### 3. Assigning Reviewers @@ -44,7 +44,7 @@ After approval is completed, system access from that IP is immediately allowed. * Click the `Save` button to close the modal and complete reviewer assignment.
-![Screenshot-2025-06-26-at-3.57.36-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-3.57.36-PM.png) +Screenshot-2025-06-26-at-3.57.36-PM.png
@@ -54,7 +54,7 @@ After approval is completed, system access from that IP is immediately allowed. * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![Screenshot-2025-06-26-at-3.59.57-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-3.59.57-PM.png) +Screenshot-2025-06-26-at-3.59.57-PM.png
@@ -73,7 +73,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent * **Reason for Request (Required)** : Enter the reason for requesting IP address registration.
-![Screenshot-2025-08-26-at-1.22.57-AM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-08-26-at-1.22.57-AM.png) +Screenshot-2025-08-26-at-1.22.57-AM.png
If you have completed entering the request information, click the `Submit` button at the bottom of the page to submit the request. @@ -83,7 +83,7 @@ If you have completed entering the request information, click the `Submit` butto When the IP access control policy (`Require Allowed Zones for User Access`) is activated by the administrator, attempting to log in from an IP not in the allow list will block the login and redirect to a dedicated page for IP registration.
-![Screenshot-2025-07-03-at-5.05.13-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-07-03-at-5.05.13-PM.png) +Screenshot-2025-07-03-at-5.05.13-PM.png
On this page, you can request IP registration by following the procedures below. @@ -108,7 +108,7 @@ Once you submit a request, you cannot submit a new IP registration request until If the request is successfully submitted, a screen indicating that the request has been properly received will be displayed along with the message 'Your IP request has been received.'
-![Screenshot-2025-06-26-at-4.19.02-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-4.19.02-PM.png) +Screenshot-2025-06-26-at-4.19.02-PM.png
diff --git a/src/content/en/user-manual/workflow/requesting-restricted-data-access.mdx b/src/content/en/user-manual/workflow/requesting-restricted-data-access.mdx index 2d34a26c..786e022c 100644 --- a/src/content/en/user-manual/workflow/requesting-restricted-data-access.mdx +++ b/src/content/en/user-manual/workflow/requesting-restricted-data-access.mdx @@ -21,7 +21,7 @@ Requests can be made through Workflow, or through the Send Restricted Data Acces * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-restricted-data-access/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. Assigning Approvers @@ -33,7 +33,7 @@ Requests can be made through Workflow, or through the Send Restricted Data Acces * All Assignees must approve this request: All approvers must approve for the approval request to be approved.
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-restricted-data-access/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. Assigning Reviewers @@ -44,7 +44,7 @@ Requests can be made through Workflow, or through the Send Restricted Data Acces * Close the modal by clicking the `Save` button to complete reviewer assignment.
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-restricted-data-access/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. Sending Request with Post-Approval @@ -53,7 +53,7 @@ Requests can be made through Workflow, or through the Send Restricted Data Acces * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-restricted-data-access/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -79,7 +79,7 @@ From version 11.3.0, the way to specify the expiration has changed.
For poli * Click the `Submit` button at the bottom of the page to submit the request.
-![User > Workflow > Submit Request > Restricted Data Access Request > Request Summary](/user-manual/workflow/requesting-restricted-data-access/image-20251009-140741.png) +User > Workflow > Submit Request > Restricted Data Access Request > Request Summary
User > Workflow > Submit Request > Restricted Data Access Request > Request Summary
diff --git a/src/content/en/user-manual/workflow/requesting-server-access.mdx b/src/content/en/user-manual/workflow/requesting-server-access.mdx index e23bc8f9..0e7fafd2 100644 --- a/src/content/en/user-manual/workflow/requesting-server-access.mdx +++ b/src/content/en/user-manual/workflow/requesting-server-access.mdx @@ -22,7 +22,7 @@ Server Access Request grants permissions immediately upon approval, and you can * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. Assigning Approvers @@ -34,7 +34,7 @@ Server Access Request grants permissions immediately upon approval, and you can * All Assignees must approve this request: All approvers must approve for the approval request to be approved.
-![image-20240807-125743.png](/user-manual/workflow/requesting-server-access/image-20240807-125743.png) +image-20240807-125743.png
#### 3. Assigning Reviewers @@ -45,7 +45,7 @@ Server Access Request grants permissions immediately upon approval, and you can * Click the `Save` button to close the modal and complete reviewer assignment.
-![screenshot-20240807-215819.png](/user-manual/workflow/requesting-server-access/screenshot-20240807-215819.png) +screenshot-20240807-215819.png
#### 4. Sending Request with Post-Approval @@ -54,7 +54,7 @@ Server Access Request grants permissions immediately upon approval, and you can * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![image-20240807-125848.png](/user-manual/workflow/requesting-server-access/image-20240807-125848.png) +image-20240807-125848.png
@@ -65,7 +65,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent #### 5. Adding Target Servers
-![Workflow > Submit Request > Server Access Request > Step 2 > Add Servers](/user-manual/workflow/requesting-server-access/image-20240514-130023.png) +Workflow > Submit Request > Server Access Request > Step 2 > Add Servers
Workflow > Submit Request > Server Access Request > Step 2 > Add Servers
@@ -80,7 +80,7 @@ Workflow > Submit Request > Server Access Request > Step 2 > Add Ser ##### When Require Minute-Based Requests is On
-![Screenshot-2025-08-26-at-1.05.08-AM.png](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-1.05.08-AM.png) +Screenshot-2025-08-26-at-1.05.08-AM.png
* **Start Trigger** : Select the permission grant start condition. @@ -91,7 +91,7 @@ Workflow > Submit Request > Server Access Request > Step 2 > Add Ser ##### When Require Minute-Based Requests is Off
-![Screenshot-2025-08-26-at-1.07.26-AM.png](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-1.07.26-AM.png) +Screenshot-2025-08-26-at-1.07.26-AM.png
* **Access Expiration Date** : Enter the expiration date of the requested permission. The default value follows the Maximum Access Duration value in SAC configurations > Server Access Request Default Settings in the administrator page. @@ -105,7 +105,7 @@ If you open the Add Servers modal again while servers are already added to the S #### 6. Entering Request Information
-![Workflow > Submit Request > Server Access Request > Step 3](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-1.09.31-AM.png) +Workflow > Submit Request > Server Access Request > Step 3
Workflow > Submit Request > Server Access Request > Step 3
diff --git a/src/content/en/user-manual/workflow/requesting-server-privilege.mdx b/src/content/en/user-manual/workflow/requesting-server-privilege.mdx index 917050be..6b7da9ad 100644 --- a/src/content/en/user-manual/workflow/requesting-server-privilege.mdx +++ b/src/content/en/user-manual/workflow/requesting-server-privilege.mdx @@ -22,7 +22,7 @@ This feature only supports SSH protocol communication. * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. Assigning Approvers @@ -34,7 +34,7 @@ This feature only supports SSH protocol communication. * **All Assignees must approve this request** : All approvers must approve for the approval request to be approved.
-![image-20240807-130021.png](/user-manual/workflow/requesting-server-privilege/image-20240807-130021.png) +image-20240807-130021.png
#### 3. Assigning Reviewers @@ -45,7 +45,7 @@ This feature only supports SSH protocol communication. * Click the `Save` button to close the modal and complete reviewer assignment.
-![screenshot-20240807-215819.png](/user-manual/workflow/requesting-server-privilege/screenshot-20240807-215819.png) +screenshot-20240807-215819.png
#### 4. Sending Request with Post-Approval @@ -54,7 +54,7 @@ This feature only supports SSH protocol communication. * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![image-20240807-125848.png](/user-manual/workflow/requesting-server-privilege/image-20240807-125848.png) +image-20240807-125848.png
@@ -69,7 +69,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent * Select one of the Roles assigned to the user.
-![image-20250307-123347.png](/user-manual/workflow/requesting-server-privilege/image-20250307-123347.png) +image-20250307-123347.png
#### 6. Selecting Target Server @@ -79,7 +79,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent * Click the `Add` button to close the modal and complete server selection.
-![image-20250307-123829.png](/user-manual/workflow/requesting-server-privilege/image-20250307-123829.png) +image-20250307-123829.png
#### 7. Entering Commands to Use @@ -91,7 +91,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent * **Keyword** : You can enter commands as keywords. * **RegEx** : You can enter commands in regular expression format.
- ![image-20250307-124234.png](/user-manual/workflow/requesting-server-privilege/image-20250307-124234.png) + image-20250307-124234.png
* When selecting Command Template @@ -99,7 +99,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent 1. Select a template containing the permissions you want to use from the dropdown list. 2. When you select a template, the included commands (Keyword, RegEx) are displayed on the screen, but you cannot modify them directly.
- ![Screenshot-2025-07-22-at-3.43.34-PM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-07-22-at-3.43.34-PM.png) + Screenshot-2025-07-22-at-3.43.34-PM.png
@@ -119,7 +119,7 @@ Therefore, the field for entering or selecting Commands is not displayed on the ##### When Require Minute-Based Requests is On
-![Screenshot-2025-08-26-at-1.05.08-AM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-08-26-at-1.05.08-AM.png) +Screenshot-2025-08-26-at-1.05.08-AM.png
* **Start Trigger** : Select the permission grant start condition. @@ -130,7 +130,7 @@ Therefore, the field for entering or selecting Commands is not displayed on the ##### When Require Minute-Based Requests is Off
-![Screenshot-2025-08-26-at-1.14.48-AM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-08-26-at-1.14.48-AM.png) +Screenshot-2025-08-26-at-1.14.48-AM.png
* **Privilege Expiration Date** : Enter the expiration date of the requested permission. The default value follows the Maximum Access Duration value in SAC configurations > Server Privilege Request Settings in the administrator page. @@ -143,7 +143,7 @@ Therefore, the field for entering or selecting Commands is not displayed on the * **Submit** : If you have completed all the requests, click the `Submit` button to complete the submission.
-![image-20250307-124047.png](/user-manual/workflow/requesting-server-privilege/image-20250307-124047.png) +image-20250307-124047.png
diff --git a/src/content/en/user-manual/workflow/requesting-sql-export.mdx b/src/content/en/user-manual/workflow/requesting-sql-export.mdx index 8cfbd039..4267f0f6 100644 --- a/src/content/en/user-manual/workflow/requesting-sql-export.mdx +++ b/src/content/en/user-manual/workflow/requesting-sql-export.mdx @@ -22,7 +22,7 @@ This requests data export for which you do not have permission on specific DB co * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.43.46-AM.png](/user-manual/workflow/requesting-sql-export/Screenshot-2025-08-26-at-12.43.46-AM.png) +Screenshot-2025-08-26-at-12.43.46-AM.png
#### 2. Assigning Approvers @@ -34,7 +34,7 @@ This requests data export for which you do not have permission on specific DB co * **All Assignees must approve this request**: All approvers must approve for the approval request to be approved.
-![screenshot-20240807-215435.png](/user-manual/workflow/requesting-sql-export/screenshot-20240807-215435.png) +screenshot-20240807-215435.png
#### 3. Assigning Executors and Reviewers @@ -45,7 +45,7 @@ This requests data export for which you do not have permission on specific DB co * Click the `Save` button to close the modal and complete reviewer assignment.
-![screenshot-20240807-215506.png](/user-manual/workflow/requesting-sql-export/screenshot-20240807-215506.png) +screenshot-20240807-215506.png
#### 4. Sending Request with Post-Approval @@ -54,7 +54,7 @@ This requests data export for which you do not have permission on specific DB co * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![screenshot-20240807-215537.png](/user-manual/workflow/requesting-sql-export/screenshot-20240807-215537.png) +screenshot-20240807-215537.png
@@ -65,7 +65,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent #### 5. Entering Request Information
-![User > Workflow > Submit Request > SQL Export Request > Request Summary](/user-manual/workflow/requesting-sql-export/Screenshot-2025-08-26-at-12.51.52-AM.png) +User > Workflow > Submit Request > SQL Export Request > Request Summary
User > Workflow > Submit Request > SQL Export Request > Request Summary
@@ -89,7 +89,7 @@ User > Workflow > Submit Request > SQL Export Request > Request Summ Approved Export Request items become immediately downloadable upon approval completion.
-![screenshot-20240802-105329.png](/user-manual/workflow/requesting-sql-export/screenshot-20240802-105329.png) +screenshot-20240802-105329.png
1. Navigate to Workflow > Executions > To Do menu. diff --git a/src/content/en/user-manual/workflow/requesting-sql.mdx b/src/content/en/user-manual/workflow/requesting-sql.mdx index 288c7f8f..8af406ec 100644 --- a/src/content/en/user-manual/workflow/requesting-sql.mdx +++ b/src/content/en/user-manual/workflow/requesting-sql.mdx @@ -22,7 +22,7 @@ After approval, the executor can execute the approved query once and view the re * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.43.46-AM.png](/user-manual/workflow/requesting-sql/Screenshot-2025-08-26-at-12.43.46-AM.png) +Screenshot-2025-08-26-at-12.43.46-AM.png
#### 2. Assigning Approvers @@ -34,7 +34,7 @@ After approval, the executor can execute the approved query once and view the re * **All Assignees must approve this request** : All approvers must approve for the approval request to be approved.
-![image-20240807-125031.png](/user-manual/workflow/requesting-sql/image-20240807-125031.png) +image-20240807-125031.png
#### 3. Assigning Executors and Reviewers @@ -45,7 +45,7 @@ After approval, the executor can execute the approved query once and view the re * Click the `Save` button to close the modal and complete reviewer assignment.
-![screenshot-20240807-215143.png](/user-manual/workflow/requesting-sql/screenshot-20240807-215143.png) +screenshot-20240807-215143.png
#### 4. Sending Request with Post-Approval @@ -54,7 +54,7 @@ After approval, the executor can execute the approved query once and view the re * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![screenshot-20240807-215226.png](/user-manual/workflow/requesting-sql/screenshot-20240807-215226.png) +screenshot-20240807-215226.png
@@ -65,7 +65,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent #### 5. Entering Request Information
-![Screenshot-2025-08-26-at-12.47.02-AM.png](/user-manual/workflow/requesting-sql/Screenshot-2025-08-26-at-12.47.02-AM.png) +Screenshot-2025-08-26-at-12.47.02-AM.png
* **Title** : Enter the request title. @@ -85,7 +85,7 @@ A. If you select an approval rule where the administrator has not allowed Urgent Approved SQL Request items become immediately executable upon approval completion.
-![Workflow > Executions > To Do > Request Details > Execute](/user-manual/workflow/requesting-sql/screenshot-20240802-104603.png) +Workflow > Executions > To Do > Request Details > Execute
Workflow > Executions > To Do > Request Details > Execute
@@ -105,7 +105,7 @@ When approval process is enforced for DML Query execution
When performing `I In this case, the following message appears when performing queries in the Web Editor.
`[ENGINE][30105] In this DML operation, you need to get approval throgh SQL Request.`
-![Warning message in Web Editor](/user-manual/workflow/requesting-sql/image-20250629-155649.png) +Warning message in Web Editor
Warning message in Web Editor
@@ -115,7 +115,7 @@ In this case, you can click the `SEND SQL Request` button to immediately move to If it is DML, you cannot use the File attachment method in Content Type.
-![SQL Request form in Workflow](/user-manual/workflow/requesting-sql/image-20250629-161143.png) +SQL Request form in Workflow
SQL Request form in Workflow
diff --git a/src/content/en/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx b/src/content/en/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx index adc6694b..a1a04cf3 100644 --- a/src/content/en/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx +++ b/src/content/en/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx @@ -36,7 +36,7 @@ If you select "File", you cannot use the execution plan (Explain) feature.
-![image-20241029-234721.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241029-234721.png) +image-20241029-234721.png
1. Execution Plan (Explain) Options and Execution Plan Execution
Select the options at the bottom of the query editor and click the `Explain` button. @@ -46,31 +46,31 @@ If you select "File", you cannot use the execution plan (Explain) feature. 2. **JSON** : Results are displayed in JSON format.
-![image-20241029-235845.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241029-235845.png) +image-20241029-235845.png
* The number of queries (statements ending with semicolons) that can be targeted for execution plan is limited to 100. * MySQL can output Explain results in JSON format from version 5.6 onwards. Therefore, if you perform Explain on versions before 5.6, you cannot output in JSON format.
-![image-20241030-001252.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-001252.png) +image-20241030-001252.png
1. Checking Execution Plan (Explain) Results 1. Checking Table Format Results
Results are displayed as shown in the figure below. Please refer to the MySQL reference documentation for the meaning of each field.

- ![image-20241030-002325.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-002325.png) + image-20241030-002325.png
2. Checking JSON Format Results
If you select JSON and click the Explain button, results are displayed as shown in the figure below. Click `{JSON}` to view the entire JSON content.




When exporting, a popup requesting password input may appear depending on administrator settings.
- ![Click `{JSON}` to view the entire content.](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-003040.png) + Click `{JSON}` to view the entire content.
Click `{JSON}` to view the entire content.
- ![You can copy and export JSON results.](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-003129.png) + You can copy and export JSON results.
You can copy and export JSON results.
@@ -80,7 +80,7 @@ If you select "File", you cannot use the execution plan (Explain) feature. 1. Approver's Execution Plan (Explain) Result Check
Approvers can check the attached execution plan (Explain) results in the Explain Results tab and use them as reference materials for approval.
- ![image-20241030-004258.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-004258.png) + image-20241030-004258.png
diff --git a/src/content/en/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx b/src/content/en/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx index d5594336..62edd30e 100644 --- a/src/content/en/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx +++ b/src/content/en/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx @@ -21,7 +21,7 @@ Mask removal can be requested through Workflow, or through the Unmasking Request * However, when submitting in Urgent Mode, the above condition is ignored.
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. Assigning Approvers @@ -33,7 +33,7 @@ Mask removal can be requested through Workflow, or through the Unmasking Request * All Assignees must approve this request: All approvers must approve for the approval request to be approved.
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. Assigning Reviewers @@ -44,7 +44,7 @@ Mask removal can be requested through Workflow, or through the Unmasking Request * Click the `Save` button to close the modal and complete reviewer assignment.
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. Sending Request with Post-Approval @@ -53,7 +53,7 @@ Mask removal can be requested through Workflow, or through the Unmasking Request * After setting Urgent mode = On and registering the approval request, you can immediately receive permissions or perform tasks.
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -78,7 +78,7 @@ From version 11.3.0, the way to specify the expiration has changed.
For poli * Click the `Submit` button at the bottom of the page to submit the request.
-![User > Workflow > Submit Request > Unmasking Request > Request Summary](/user-manual/workflow/requesting-unmasking-mask-removal-request/image-20251009-135940.png) +User > Workflow > Submit Request > Unmasking Request > Request Summary
User > Workflow > Submit Request > Unmasking Request > Request Summary
diff --git a/src/content/ja/administrator-manual.mdx b/src/content/ja/administrator-manual.mdx index 06c20dcf..ef13987b 100644 --- a/src/content/ja/administrator-manual.mdx +++ b/src/content/ja/administrator-manual.mdx @@ -14,7 +14,7 @@ QueryPieの管理者は、QueryPie WebまたはAPIを通じて、リソースお このボタンをクリックして管理者ページを新しいタブで開くことができます。
-![GNB内の管理者ページアクセスポイント](/administrator-manual/screenshot-20240801-145006.png) +GNB内の管理者ページアクセスポイント
GNB内の管理者ページアクセスポイント
diff --git a/src/content/ja/administrator-manual/audit/database-logs/access-control-logs.mdx b/src/content/ja/administrator-manual/audit/database-logs/access-control-logs.mdx index c580eb16..37c4c3e5 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/access-control-logs.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/access-control-logs.mdx @@ -11,7 +11,7 @@ QueryPieユーザー/グループに付与されるDBコネクションに対す ### DB Access Control Logs照会
-![Administrator > Audit > Databases > Access Control Logs](/administrator-manual/audit/database-logs/access-control-logs/image-20240730-072419.png) +Administrator > Audit > Databases > Access Control Logs
Administrator > Audit > Databases > Access Control Logs
@@ -27,7 +27,7 @@ Administrator > Audit > Databases > Access Control Logs 5. **DB Host** : DBホスト 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240730-073211.png](/administrator-manual/audit/database-logs/access-control-logs/image-20240730-073211.png) + image-20240730-073211.png
1. **Connection Name** : DBコネクション名 2. **Database Type** : データベースタイプ diff --git a/src/content/ja/administrator-manual/audit/database-logs/account-lock-history.mdx b/src/content/ja/administrator-manual/audit/database-logs/account-lock-history.mdx index d5936f37..0c9faf15 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/account-lock-history.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/account-lock-history.mdx @@ -12,7 +12,7 @@ QueryPieのユーザー別コネクションパスワード失敗および長期 ### DB Account Lock History照会
-![Administrator > Audit > Databases > Account Lock History](/administrator-manual/audit/database-logs/account-lock-history/image-20240730-070724.png) +Administrator > Audit > Databases > Account Lock History
Administrator > Audit > Databases > Account Lock History
@@ -23,7 +23,7 @@ Administrator > Audit > Databases > Account Lock History 3. テーブル左上の検索欄を通じてユーザー名で検索が可能です。 4. 検索フィールド右側フィルターボタンをクリックして **Action At** に対する日時範囲を再指定してフィルタリングが可能です。
- ![image-20240730-071155.png](/administrator-manual/audit/database-logs/account-lock-history/image-20240730-071155.png) + image-20240730-071155.png
1. **Connection Name** : 接続したDBコネクション名 2. **Database Type** : データベースタイプ diff --git a/src/content/ja/administrator-manual/audit/database-logs/db-access-history.mdx b/src/content/ja/administrator-manual/audit/database-logs/db-access-history.mdx index fb4a9d09..ee65c5ed 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/db-access-history.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/db-access-history.mdx @@ -11,7 +11,7 @@ title: 'DB Access History' ### DB Access History照会
-![Administrator > Audit > Databases > DB Access History](/administrator-manual/audit/database-logs/db-access-history/image-20240730-070842.png) +Administrator > Audit > Databases > DB Access History
Administrator > Audit > Databases > DB Access History
@@ -25,7 +25,7 @@ Administrator > Audit > Databases > DB Access History 3. **Client IP** : ユーザーIP 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240730-064139.png](/administrator-manual/audit/database-logs/db-access-history/image-20240730-064139.png) + image-20240730-064139.png
1. **Connection Name** : 接続したDBコネクション名 2. **Database Type** : データベースタイプ @@ -60,7 +60,7 @@ Administrator > Audit > Databases > DB Access History 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Databases > DB Access History > DB Access History Details](/administrator-manual/audit/database-logs/db-access-history/image-20240730-065045.png) +Administrator > Audit > Databases > DB Access History > DB Access History Details
Administrator > Audit > Databases > DB Access History > DB Access History Details
diff --git a/src/content/ja/administrator-manual/audit/database-logs/dml-snapshots.mdx b/src/content/ja/administrator-manual/audit/database-logs/dml-snapshots.mdx index 451edd6f..a5ea2b5f 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/dml-snapshots.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/dml-snapshots.mdx @@ -13,7 +13,7 @@ QueryPieでINSERT / UPDATE / DELETEクエリ実行完了時前後データを記 ### DML Snapshots照会
-![Administrator > Audit > Databases > DML Snapshots](/administrator-manual/audit/database-logs/dml-snapshots/image-20240730-094404.png) +Administrator > Audit > Databases > DML Snapshots
Administrator > Audit > Databases > DML Snapshots
@@ -24,7 +24,7 @@ Administrator > Audit > Databases > DML Snapshots 3. テーブル左上の検索欄を通じてユーザー名で検索が可能です。 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240730-094947.png](/administrator-manual/audit/database-logs/dml-snapshots/image-20240730-094947.png) + image-20240730-094947.png
1. **Connection Name** : 接続したDBコネクション名 2. **Executed At** : 実行日時 @@ -53,7 +53,7 @@ Administrator > Audit > Databases > DML Snapshots 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Databases > DML Snapshots > DML Snapshot Details](/administrator-manual/audit/database-logs/dml-snapshots/image-20240730-095257.png) +Administrator > Audit > Databases > DML Snapshots > DML Snapshot Details
Administrator > Audit > Databases > DML Snapshots > DML Snapshot Details
diff --git a/src/content/ja/administrator-manual/audit/database-logs/policy-audit-logs.mdx b/src/content/ja/administrator-manual/audit/database-logs/policy-audit-logs.mdx index 19b452e0..0f7474f2 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/policy-audit-logs.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/policy-audit-logs.mdx @@ -10,7 +10,7 @@ title: 'Policy Audit Logs' 新規DAC政策を有効化した場合記録が開始され、メニューに露出されます。
-![Audit > Databases > Policy Audit Logs](/administrator-manual/audit/database-logs/policy-audit-logs/image-20250629-174715.png) +Audit > Databases > Policy Audit Logs
Audit > Databases > Policy Audit Logs
diff --git a/src/content/ja/administrator-manual/audit/database-logs/policy-exception-logs.mdx b/src/content/ja/administrator-manual/audit/database-logs/policy-exception-logs.mdx index 72d246d3..46a65216 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/policy-exception-logs.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/policy-exception-logs.mdx @@ -11,7 +11,7 @@ title: 'Policy Exception logs' リストで行をクリックすると特定の政策例外の詳細内容を見ることができます。
-![Policy Exception Logs](/administrator-manual/audit/database-logs/policy-exception-logs/image-20250725-132239.png) +Policy Exception Logs
Policy Exception Logs
diff --git a/src/content/ja/administrator-manual/audit/database-logs/query-audit.mdx b/src/content/ja/administrator-manual/audit/database-logs/query-audit.mdx index 02c2302c..7f96132f 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/query-audit.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/query-audit.mdx @@ -11,7 +11,7 @@ title: 'Query Audit' ### Query Audit照会
-![Administrator > Audit > Databases > Query Audit](/administrator-manual/audit/database-logs/query-audit/image-20240730-090702.png) +Administrator > Audit > Databases > Query Audit
Administrator > Audit > Databases > Query Audit
@@ -24,7 +24,7 @@ Administrator > Audit > Databases > Query Audit 2. **Table(s)** : 呼び出しテーブル名 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240730-091338.png](/administrator-manual/audit/database-logs/query-audit/image-20240730-091338.png) + image-20240730-091338.png
1. **Connection Name** : 接続したDBコネクション名 2. **Database Type** : データベースタイプ @@ -81,7 +81,7 @@ Administrator > Audit > Databases > Query Audit 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Databases > Query Audit > Query Audit Details](/administrator-manual/audit/database-logs/query-audit/image-20240730-091103.png) +Administrator > Audit > Databases > Query Audit > Query Audit Details
Administrator > Audit > Databases > Query Audit > Query Audit Details
diff --git a/src/content/ja/administrator-manual/audit/database-logs/running-queries.mdx b/src/content/ja/administrator-manual/audit/database-logs/running-queries.mdx index 4f157f4c..7ab7b3dc 100644 --- a/src/content/ja/administrator-manual/audit/database-logs/running-queries.mdx +++ b/src/content/ja/administrator-manual/audit/database-logs/running-queries.mdx @@ -19,7 +19,7 @@ import { Callout } from 'nextra/components' ### Running Queries照会
-![Administrator > Audit > Databases > Running Queries](/administrator-manual/audit/database-logs/running-queries/image-20240730-081612.png) +Administrator > Audit > Databases > Running Queries
Administrator > Audit > Databases > Running Queries
@@ -29,7 +29,7 @@ Administrator > Audit > Databases > Running Queries 2. 当日基準で降順でログが照会されます。 3. テーブル左上のフィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240730-081641.png](/administrator-manual/audit/database-logs/running-queries/image-20240730-081641.png) + image-20240730-081641.png
1. **SQL Type** : SQL構文タイプ 2. **Action At** : クエリ実行日時範囲 @@ -66,7 +66,7 @@ Administrator > Audit > Databases > Running Queries 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Databases > Running Queries > Running Query Details](/administrator-manual/audit/database-logs/running-queries/image-20240730-080947.png) +Administrator > Audit > Databases > Running Queries > Running Query Details
Administrator > Audit > Databases > Running Queries > Running Query Details
diff --git a/src/content/ja/administrator-manual/audit/general-logs/activity-logs.mdx b/src/content/ja/administrator-manual/audit/general-logs/activity-logs.mdx index 90be865a..0daac061 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/activity-logs.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/activity-logs.mdx @@ -14,7 +14,7 @@ Activity logsでは、**管理者**によって実行されるリソース登録 ### Activity Logsの照会
-![Administrator > Audit > General > Activity Logs](/administrator-manual/audit/general-logs/activity-logs/screenshot-20240722-191106.png) +Administrator > Audit > General > Activity Logs
Administrator > Audit > General > Activity Logs
@@ -35,7 +35,7 @@ Administrator > Audit > General > Activity Logs ### Activity Logs詳細内容の照会
-![Administrator > Audit > General > Activity Logs > Activity Logs Details](/administrator-manual/audit/general-logs/activity-logs/image-20251009-024238.png) +Administrator > Audit > General > Activity Logs > Activity Logs Details
Administrator > Audit > General > Activity Logs > Activity Logs Details
diff --git a/src/content/ja/administrator-manual/audit/general-logs/admin-role-history.mdx b/src/content/ja/administrator-manual/audit/general-logs/admin-role-history.mdx index 3b2c5f4d..d59bd2ef 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/admin-role-history.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/admin-role-history.mdx @@ -14,7 +14,7 @@ Administrator > General > User Management > Usersページで特定の ### Admin Role Historyの照会
-![Administrator > Audit > General > Admin Role History](/administrator-manual/audit/general-logs/admin-role-history/screenshot-20240722-190405.png) +Administrator > Audit > General > Admin Role History
Administrator > Audit > General > Admin Role History
diff --git a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels.mdx b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels.mdx index 14bc8bc1..157aab25 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels.mdx @@ -20,7 +20,7 @@ QueryPieと接続されたReverse Tunnelsセッションをモニタリングす ### Reverse Tunnels照会
-![Admin Page > Audit > General > Reverse Tunnels](/administrator-manual/audit/general-logs/reverse-tunnels/image-20250116-123838.png) +Admin Page > Audit > General > Reverse Tunnels
Admin Page > Audit > General > Reverse Tunnels
diff --git a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx index 94987074..0623f32b 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel.mdx @@ -14,7 +14,7 @@ QueryPieと他のNetwork Zoneにあるリソースとの通信手段としてRev ### Reverse Tunnelをクラスターに適用する
-![Administrator > Kubernetes > Connection Management > Clusters > List Details](/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-clusters-through-reverse-tunnel/image-20250116-124402.png) +Administrator > Kubernetes > Connection Management > Clusters > List Details
Administrator > Kubernetes > Connection Management > Clusters > List Details
diff --git a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx index f21ae8bc..7f0e875b 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel.mdx @@ -14,7 +14,7 @@ QueryPieと他のNetwork Zoneにあるリソースと通信する手段として ### Reverse Tunnels DB Connectionに適用する
-![Admin Page > Servers > Connection Management > DB Connections](/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-db-through-reverse-tunnel/image-20250512-122312.png) +Admin Page > Servers > Connection Management > DB Connections
Admin Page > Servers > Connection Management > DB Connections
diff --git a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx index 5228d950..13f784d0 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel.mdx @@ -14,7 +14,7 @@ QueryPieと他のNetwork Zoneにあるリソースと通信する手段として ### Reverse Tunnelsをサーバーに適用する
-![Admin Page > Servers > Connection Management > Servers](/administrator-manual/audit/general-logs/reverse-tunnels/communicating-with-servers-through-reverse-tunnel/image-20241209-134405.png) +Admin Page > Servers > Connection Management > Servers
Admin Page > Servers > Connection Management > Servers
diff --git a/src/content/ja/administrator-manual/audit/general-logs/user-access-history.mdx b/src/content/ja/administrator-manual/audit/general-logs/user-access-history.mdx index 1cffa93a..b30f7163 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/user-access-history.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/user-access-history.mdx @@ -12,7 +12,7 @@ title: 'User Access History' ### User Access Historyの照会
-![Administrator > Audit > General > User Access History](/administrator-manual/audit/general-logs/user-access-history/image-20240714-063443.png) +Administrator > Audit > General > User Access History
Administrator > Audit > General > User Access History
@@ -37,7 +37,7 @@ Administrator > Audit > General > User Access History User Access History一覧で個別ログをクリックすると、ログに関する詳細情報を確認できます。
-![Administrator > Audit > General > User Access History > Details](/administrator-manual/audit/general-logs/user-access-history/image-20240721-074544.png) +Administrator > Audit > General > User Access History > Details
Administrator > Audit > General > User Access History > Details
diff --git a/src/content/ja/administrator-manual/audit/general-logs/workflow-logs.mdx b/src/content/ja/administrator-manual/audit/general-logs/workflow-logs.mdx index 4453631d..ca190845 100644 --- a/src/content/ja/administrator-manual/audit/general-logs/workflow-logs.mdx +++ b/src/content/ja/administrator-manual/audit/general-logs/workflow-logs.mdx @@ -14,7 +14,7 @@ QueryPieワークフロー承認受付および承認履歴を照会するペー ### Workflow Logs照会
-![Administrator > Audit > General > Workflow Logs](/administrator-manual/audit/general-logs/workflow-logs/image-20241029-052424.png) +Administrator > Audit > General > Workflow Logs
Administrator > Audit > General > Workflow Logs
diff --git a/src/content/ja/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx b/src/content/ja/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx index 9941f3f5..8d4a7af0 100644 --- a/src/content/ja/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx +++ b/src/content/ja/administrator-manual/audit/kubernetes-logs/kubernetes-role-history.mdx @@ -11,7 +11,7 @@ title: 'Kubernetes Role History' ### Kubernetes Role Historyの照会
-![Administrator > Audit > Kubernetes > Kubernetes Role History](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-083952.png) +Administrator > Audit > Kubernetes > Kubernetes Role History
Administrator > Audit > Kubernetes > Kubernetes Role History
@@ -25,7 +25,7 @@ Administrator > Audit > Kubernetes > Kubernetes Role History 3. **Role Name** : Kubernetesアクセス権限役割名 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240721-084201.png](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-084201.png) + image-20240721-084201.png
1. **Event** : Kubernetesロールイベントタイプ 1. **Role Granted** : Role付与履歴 @@ -53,7 +53,7 @@ Administrator > Audit > Kubernetes > Kubernetes Role History 1. 各行をクリックすると詳細情報照会が可能です。
- ![Administrator > Audit > Kubernetes > Kubernetes Role History > Kubernetes Role History Details](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-084057.png) + Administrator > Audit > Kubernetes > Kubernetes Role History > Kubernetes Role History Details
Administrator > Audit > Kubernetes > Kubernetes Role History > Kubernetes Role History Details
@@ -75,7 +75,7 @@ Administrator > Audit > Kubernetes > Kubernetes Role History 3. **Version** : 割り当てられている政策のバージョン * リンクを押すと政策コードを照会できるようにポップアップモーダルが現れます。
- ![image-20240721-084129.png](/administrator-manual/audit/kubernetes-logs/kubernetes-role-history/image-20240721-084129.png) + image-20240721-084129.png
1. 付与されていた当時のPolicy Snapshotを見せます。 * 該当Policyが削除されても記録が残ります。 diff --git a/src/content/ja/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx b/src/content/ja/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx index 94df8800..8cfec97f 100644 --- a/src/content/ja/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx +++ b/src/content/ja/administrator-manual/audit/kubernetes-logs/pod-session-recordings.mdx @@ -12,7 +12,7 @@ title: 'Pod Session Recordings' ### Pod Session Recordingsの照会
-![Administrator > Audit > Kubernetes > Pod Session Recordings](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082407.png) +Administrator > Audit > Kubernetes > Pod Session Recordings
Administrator > Audit > Kubernetes > Pod Session Recordings
@@ -28,7 +28,7 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 5. **Client Name** : ユーザークライアント名/バージョン（例. kubectl/v1.27.3） 4. 検索フィールド右側フィルターボタンをクリックして **Action At** に対する日時範囲を再指定してフィルタリングが可能です。
- ![image-20240721-082446.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082446.png) + image-20240721-082446.png
5. テーブル右上のリフレッシュボタンを通じてログ一覧を最新化できます。 6. テーブルで以下のカラム情報を提供します: @@ -48,12 +48,12 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 1. 各行のAction Atのリンクをクリックするとセッションレコーディング内訳の再生が可能です。 2. Action Atのリンクをクリックするとモーダルが実行され、再生のための初期ダウンローディングプロセスを見せるモーダルが現れます。
- ![image-20240425-022156.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240425-022156.png) + image-20240425-022156.png
3. 録画されたファイルのサイズが700MBを超過するかどうかによって再生画面を露出するかダウンロードボタンを露出します。 1. **700MB未満**
- ![image-20240721-082651.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082651.png) + image-20240721-082651.png
1. 上部に基本情報が露出され、下部にReplay再生画面が露出されます。 1. **Name** : 実行者名 @@ -65,7 +65,7 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 3. `Close`ボタンを押すと窓が閉じます。 2. **700MB以上**
- ![image-20240618-053333.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240618-053333.png) + image-20240618-053333.png
1. 再生画面内に実行不可能文句とともにダウンロードボタンを提供します。 1. ファイルサイズが700MBを超過してセッションを再生できません。 @@ -73,8 +73,8 @@ Administrator > Audit > Kubernetes > Pod Session Recordings 2. `Download`ボタンを押すとダウンロードが進行してローカルにファイルが生成されます。 1. Administrator > General > Company Management > Security > Others に位置する `Export a file with Encryption`共通オプションが`Required`でアクティブになっている場合、該当ダウンロード時に暗号化モーダルが追加で現れ、該当モーダル以降にダウンロードを実行します。
- ![image-20240721-082733.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240721-082733.png) + image-20240721-082733.png
- ![image-20240425-025317.png](/administrator-manual/audit/kubernetes-logs/pod-session-recordings/image-20240425-025317.png) + image-20240425-025317.png
diff --git a/src/content/ja/administrator-manual/audit/kubernetes-logs/request-audit.mdx b/src/content/ja/administrator-manual/audit/kubernetes-logs/request-audit.mdx index 499f8e9d..74c26c7d 100644 --- a/src/content/ja/administrator-manual/audit/kubernetes-logs/request-audit.mdx +++ b/src/content/ja/administrator-manual/audit/kubernetes-logs/request-audit.mdx @@ -11,7 +11,7 @@ title: 'Request Audit' ### Request Auditの照会
-![image-20240721-082824.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240721-082824.png) +image-20240721-082824.png
1. Administrator > Audit > Kubernetes > Request Auditメニューに移動します。 @@ -21,7 +21,7 @@ title: 'Request Audit' 2. **Cluster Name** : クエリパイ上に登録されたクラスター名 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240721-082906.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240721-082906.png) + image-20240721-082906.png
1. **Verb** : 呼び出された特定のKubernetes APIアクション * `get`, `list`, `watch`, `create`, `update`, `patch`, `delete`, `deletecollection` @@ -55,7 +55,7 @@ title: 'Request Audit' 1. 各行をクリックすると詳細情報照会が可能です。
- ![image-20250116-121412.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20250116-121412.png) + image-20250116-121412.png
1. 最上位には基本イベントに基づく情報を露出します: 1. **Result** : API呼び出し成功/失敗の有無 @@ -76,11 +76,11 @@ title: 'Request Audit' 1. セッションレコーディングが発生されたログに限り該当フィールドが詳細ページで照会可能です。 2. Pod exec APIで実行時、該当セッションに対するレコーディングが進行され、該当「Session Recording」文句にハイパーリンクが含まれます。
- ![image-20240512-055657.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240512-055657.png) + image-20240512-055657.png
3. リンククリック時、関連セッションレコーディングがプレイされます。
- ![image-20240721-082651.png](/administrator-manual/audit/kubernetes-logs/request-audit/image-20240721-082651.png) + image-20240721-082651.png
14. 中間段にはAPI呼び出し内訳に基づく情報を露出します: 1. **Verb** : 呼び出された特定のKubernetes APIアクション diff --git a/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx b/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx index b8438cfd..a240d917 100644 --- a/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx +++ b/src/content/ja/administrator-manual/audit/reports/audit-log-export.mdx @@ -62,7 +62,7 @@ Audit Log Export機能追加に伴い、各ログ画面で提供されていた' ### Audit Log Export一覧の照会
-![Administrator > Audit > General > Audit Log Export](/administrator-manual/audit/reports/audit-log-export/image-20240714-063656.png) +Administrator > Audit > General > Audit Log Export
Administrator > Audit > General > Audit Log Export
@@ -84,7 +84,7 @@ Administrator > Audit > General > Audit Log Export 該当ボタンクリック時、以下のような画面が現れます。
-![Administrator > Audit > General > Audit Log Export > Create New Task](/administrator-manual/audit/reports/audit-log-export/screenshot-20250116-131805.png) +Administrator > Audit > General > Audit Log Export > Create New Task
Administrator > Audit > General > Audit Log Export > Create New Task
diff --git a/src/content/ja/administrator-manual/audit/reports/reports.mdx b/src/content/ja/administrator-manual/audit/reports/reports.mdx index 70d9fd4f..671e5d1e 100644 --- a/src/content/ja/administrator-manual/audit/reports/reports.mdx +++ b/src/content/ja/administrator-manual/audit/reports/reports.mdx @@ -685,7 +685,7 @@ AuditメニューでReports > Reportsメニューに進入するとレポー
-![Administrator > Audit > Reports > Reports](/administrator-manual/audit/reports/reports/screenshot-20241223-112238.png) +Administrator > Audit > Reports > Reports
Administrator > Audit > Reports > Reports
@@ -724,7 +724,7 @@ Administrator > Audit > Reports > Reports
-![Administrator > Audit > Reports > Reports > Report Detail](/administrator-manual/audit/reports/reports/screenshot-20241223-112524.png) +Administrator > Audit > Reports > Reports > Report Detail
Administrator > Audit > Reports > Reports > Report Detail
@@ -763,7 +763,7 @@ Administrator > Audit > Reports > Reports > Report Detail タスク名、レポートタイプ、スケジューリング関連内容を入力し、セクション単位でレポート出力項目および適用するフィルターを指定できます。`+ Add Section`ボタンをクリックしてセクションを追加できます。
-![Administrator > Audit > Reports > Reports > Create](/administrator-manual/audit/reports/reports/screenshot-20241209-104337.png) +Administrator > Audit > Reports > Reports > Create
Administrator > Audit > Reports > Reports > Create
@@ -799,7 +799,7 @@ Administrator > Audit > Reports > Reports > Create ### レポート複製**[10.2.2]**
-![Administrator > Audit > Reports > Reports - Duplicate Task](/administrator-manual/audit/reports/reports/screenshot-20241223-104529.png) +Administrator > Audit > Reports > Reports - Duplicate Task
Administrator > Audit > Reports > Reports - Duplicate Task
diff --git a/src/content/ja/administrator-manual/audit/server-logs/access-control-logs.mdx b/src/content/ja/administrator-manual/audit/server-logs/access-control-logs.mdx index 90a48564..825afb85 100644 --- a/src/content/ja/administrator-manual/audit/server-logs/access-control-logs.mdx +++ b/src/content/ja/administrator-manual/audit/server-logs/access-control-logs.mdx @@ -11,7 +11,7 @@ title: 'Access Control Logs' ### Server Access Control Logsの照会
-![Administrator > Audit > Servers > Access Control Logs](/administrator-manual/audit/server-logs/access-control-logs/image-20240728-174950.png) +Administrator > Audit > Servers > Access Control Logs
Administrator > Audit > Servers > Access Control Logs
@@ -28,7 +28,7 @@ Administrator > Audit > Servers > Access Control Logs 6. **Account** : サーバーAccount 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240728-174439.png](/administrator-manual/audit/server-logs/access-control-logs/image-20240728-174439.png) + image-20240728-174439.png
1. **Event** : イベントタイプ 1. **Access Control Granted** : Permission付与履歴 @@ -61,7 +61,7 @@ Administrator > Audit > Servers > Access Control Logs 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Servers > Access Control Logs > Access Control Logs Detail](/administrator-manual/audit/server-logs/access-control-logs/image-20240728-175354.png) +Administrator > Audit > Servers > Access Control Logs > Access Control Logs Detail
Administrator > Audit > Servers > Access Control Logs > Access Control Logs Detail
diff --git a/src/content/ja/administrator-manual/audit/server-logs/account-lock-history.mdx b/src/content/ja/administrator-manual/audit/server-logs/account-lock-history.mdx index 5de215db..8aa3704e 100644 --- a/src/content/ja/administrator-manual/audit/server-logs/account-lock-history.mdx +++ b/src/content/ja/administrator-manual/audit/server-logs/account-lock-history.mdx @@ -12,7 +12,7 @@ QueryPieのユーザー別サーバー接続権限ロック履歴を表示しま ### Server Account Lock Historyの照会
-![Administrator > Audit > Servers > Server Account Lock History](/administrator-manual/audit/server-logs/account-lock-history/image-20240728-175941.png) +Administrator > Audit > Servers > Server Account Lock History
Administrator > Audit > Servers > Server Account Lock History
@@ -28,7 +28,7 @@ Administrator > Audit > Servers > Server Account Lock History 5. **Server Name** : 接続サーバー名 4. 検索フィールド右側フィルターボタンをクリックして **Action At** に対する日時範囲を再指定してフィルタリングが可能です。
- ![image-20240728-180318.png](/administrator-manual/audit/server-logs/account-lock-history/image-20240728-180318.png) + image-20240728-180318.png
1. **Event** : イベントタイプ 1. **Account Locked** : ユーザーのアカウントロックイベント diff --git a/src/content/ja/administrator-manual/audit/server-logs/command-audit.mdx b/src/content/ja/administrator-manual/audit/server-logs/command-audit.mdx index 1d49f59c..b4266154 100644 --- a/src/content/ja/administrator-manual/audit/server-logs/command-audit.mdx +++ b/src/content/ja/administrator-manual/audit/server-logs/command-audit.mdx @@ -14,7 +14,7 @@ Windows Serverの場合、マウスクリック、キーボード入力、実行 ### Command Auditの照会
-![Administrator > Audit > Servers > Command Audit](/administrator-manual/audit/server-logs/command-audit/image-20240728-171227.png) +Administrator > Audit > Servers > Command Audit
Administrator > Audit > Servers > Command Audit
@@ -29,7 +29,7 @@ Administrator > Audit > Servers > Command Audit * **Role** : 接続Role * 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240728-171533.png](/administrator-manual/audit/server-logs/command-audit/image-20240728-171533.png) + image-20240728-171533.png
* **Server OS** : 接続したサーバーのOS * **Protocol** : 接続使用したProtocol @@ -51,7 +51,7 @@ Administrator > Audit > Servers > Command Audit 11.3.0でフィルターを使用する際、Action Typeの項目を複数選択できるよう変更されました。
-![フィルターのAction Typeで複数の項目を選択した例](/administrator-manual/audit/server-logs/command-audit/image-20250930-083734.png) +フィルターのAction Typeで複数の項目を選択した例
フィルターのAction Typeで複数の項目を選択した例
@@ -87,7 +87,7 @@ Administrator > Audit > Servers > Command Audit
-![Administrator > Audit > Servers > Command Audit > Command Audit Details](/administrator-manual/audit/server-logs/command-audit/image-20241209-125101.png) +Administrator > Audit > Servers > Command Audit > Command Audit Details
Administrator > Audit > Servers > Command Audit > Command Audit Details
diff --git a/src/content/ja/administrator-manual/audit/server-logs/server-access-history.mdx b/src/content/ja/administrator-manual/audit/server-logs/server-access-history.mdx index 475d00eb..674a9bce 100644 --- a/src/content/ja/administrator-manual/audit/server-logs/server-access-history.mdx +++ b/src/content/ja/administrator-manual/audit/server-logs/server-access-history.mdx @@ -11,7 +11,7 @@ title: 'Server Access History' ### Server Access Historyの照会
-![Administrator > Audit > Servers > Server Access History](/administrator-manual/audit/server-logs/server-access-history/image-20240728-165641.png) +Administrator > Audit > Servers > Server Access History
Administrator > Audit > Servers > Server Access History
@@ -30,7 +30,7 @@ Administrator > Audit > Servers > Server Access History 8. **Role** : 接続Role 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240728-170045.png](/administrator-manual/audit/server-logs/server-access-history/image-20240728-170045.png) + image-20240728-170045.png
1. **Server OS** : 接続したサーバーのOS 2. **Protocol** : 接続使用したProtocol @@ -63,7 +63,7 @@ Administrator > Audit > Servers > Server Access History
-![Administrator > Audit > Servers > Server Access History > Server Access History Details](/administrator-manual/audit/server-logs/server-access-history/image-20241209-142526.png) +Administrator > Audit > Servers > Server Access History > Server Access History Details
Administrator > Audit > Servers > Server Access History > Server Access History Details
diff --git a/src/content/ja/administrator-manual/audit/server-logs/server-role-history.mdx b/src/content/ja/administrator-manual/audit/server-logs/server-role-history.mdx index f76b11d4..5e794e7d 100644 --- a/src/content/ja/administrator-manual/audit/server-logs/server-role-history.mdx +++ b/src/content/ja/administrator-manual/audit/server-logs/server-role-history.mdx @@ -11,7 +11,7 @@ title: 'Server Role History' ### Server Role Historyの照会
-![Administrator > Audit > Servers > Server Role History](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174347.png) +Administrator > Audit > Servers > Server Role History
Administrator > Audit > Servers > Server Role History
@@ -25,7 +25,7 @@ Administrator > Audit > Servers > Server Role History 3. **Role Name** : サーバーアクセス権限役割名 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240728-174439.png](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174439.png) + image-20240728-174439.png
1. **Event** : イベントタイプ 1. **Role Granted** : Role付与履歴 @@ -51,7 +51,7 @@ Administrator > Audit > Servers > Server Role History 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Servers > Server Role History > Server Role History Details](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174604.png) +Administrator > Audit > Servers > Server Role History > Server Role History Details
Administrator > Audit > Servers > Server Role History > Server Role History Details
@@ -71,7 +71,7 @@ Administrator > Audit > Servers > Server Role History > Server Role * **Version** : 割り当てられている政策のバージョン * リンクを押すと政策コードを照会できるようにポップアップモーダルが現れます。
- ![image-20240728-174822.png](/administrator-manual/audit/server-logs/server-role-history/image-20240728-174822.png) + image-20240728-174822.png
1. 付与されていた当時のPolicy Snapshotを見せます。 * 該当Policyが削除されても記録が残ります。 diff --git a/src/content/ja/administrator-manual/audit/server-logs/session-logs.mdx b/src/content/ja/administrator-manual/audit/server-logs/session-logs.mdx index caae7f88..a003373b 100644 --- a/src/content/ja/administrator-manual/audit/server-logs/session-logs.mdx +++ b/src/content/ja/administrator-manual/audit/server-logs/session-logs.mdx @@ -12,7 +12,7 @@ title: 'Session Logs' ### Session Logsの照会
-![Administrator > Audit > Servers > Session Logs](/administrator-manual/audit/server-logs/session-logs/image-20240728-173024.png) +Administrator > Audit > Servers > Session Logs
Administrator > Audit > Servers > Session Logs
@@ -30,7 +30,7 @@ Administrator > Audit > Servers > Session Logs 7. **Client** **Name** : ユーザーの接続方式 4. 検索フィールド右側フィルターボタンをクリックして **Action At** に対する日時範囲を再指定してフィルタリングが可能です。
- ![image-20240728-173136.png](/administrator-manual/audit/server-logs/session-logs/image-20240728-173136.png) + image-20240728-173136.png
1. **Server OS** : 接続したサーバーのOS 2. **Protocol** : 接続使用したProtocol @@ -63,7 +63,7 @@ Administrator > Audit > Servers > Session Logs 1. **700MB未満**
- ![image-20240728-173517.png](/administrator-manual/audit/server-logs/session-logs/image-20240728-173517.png) + image-20240728-173517.png
1. 上部に基本情報が露出され下部にReplay再生画面が露出されます。 1. **Name** : 実行者名 @@ -80,8 +80,8 @@ Administrator > Audit > Servers > Session Logs 2. `Download`ボタンを押すとダウンロードが進行されローカルにファイルが生成されます。 1. Administrator > General > Company Management > Security > Others に位置する `Export a file with Encryption`共通オプションが`Required`で有効化されている場合、該当ダウンロード時暗号化モーダルが追加で現れ、該当モーダル後にダウンロードを実行します。
- ![image-20240721-082733.png](/administrator-manual/audit/server-logs/session-logs/image-20240721-082733.png) + image-20240721-082733.png
- ![image-20240425-025317.png](/administrator-manual/audit/server-logs/session-logs/image-20240425-025317.png) + image-20240425-025317.png
diff --git a/src/content/ja/administrator-manual/audit/server-logs/session-monitoring-moved.mdx b/src/content/ja/administrator-manual/audit/server-logs/session-monitoring-moved.mdx index 44c919e8..c55d8719 100644 --- a/src/content/ja/administrator-manual/audit/server-logs/session-monitoring-moved.mdx +++ b/src/content/ja/administrator-manual/audit/server-logs/session-monitoring-moved.mdx @@ -18,7 +18,7 @@ QueryPieを通じたサーバー接続セッションを照会できます。 ### Session Monitoring照会
-![Administrator > Audit > Servers > Session Monitoring](/administrator-manual/audit/server-logs/session-monitoring-moved/image-20240728-173632.png) +Administrator > Audit > Servers > Session Monitoring
Administrator > Audit > Servers > Session Monitoring
@@ -41,7 +41,7 @@ Administrator > Audit > Servers > Session Monitoring ### Session強制終了
-![image-20240728-173640.png](/administrator-manual/audit/server-logs/session-monitoring-moved/image-20240728-173640.png) +image-20240728-173640.png
1. Administrator > Audit > Servers > Server Monitoringメニューに移動します。 diff --git a/src/content/ja/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx b/src/content/ja/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx index 86a1211b..78fc2e5c 100644 --- a/src/content/ja/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx +++ b/src/content/ja/administrator-manual/audit/web-app-logs/jit-access-control-logs.mdx @@ -11,7 +11,7 @@ title: 'JIT Access Control Logs' ### JIT Access Control Logsの照会
-![Administrator > Audit > Web Apps > JIT Access Control Logs](/administrator-manual/audit/web-app-logs/jit-access-control-logs/image-20250629-174842.png) +Administrator > Audit > Web Apps > JIT Access Control Logs
Administrator > Audit > Web Apps > JIT Access Control Logs
@@ -22,7 +22,7 @@ Administrator > Audit > Web Apps > JIT Access Control Logs 3. テーブル左上の検索欄を通じて以下の条件で検索が可能です。
a. **User Name** : ユーザー名
b. **User Email** : ユーザーメール
c. **Web App Name** : ウェブアプリケーション名 4. 検索フィールド右側フィルターボタンをクリックしてAND条件で以下のフィルタリングが可能です。
- ![image-20250629-174904.png](/administrator-manual/audit/web-app-logs/jit-access-control-logs/image-20250629-174904.png) + image-20250629-174904.png
1. **Event** : イベントタイプ(JIT Access Granted/JIT Access Revoked) 2. **Action At** : アクション発生日時範囲 diff --git a/src/content/ja/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx b/src/content/ja/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx index ee0fe10c..d764d13b 100644 --- a/src/content/ja/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx +++ b/src/content/ja/administrator-manual/audit/web-app-logs/user-activity-recordings.mdx @@ -13,7 +13,7 @@ import { Callout } from 'nextra/components' ### User Activity Recordingsの照会
-![Administrator > Audit > Web Apps > User Activity Recordings](/administrator-manual/audit/web-app-logs/user-activity-recordings/image-20250629-175520.png) +Administrator > Audit > Web Apps > User Activity Recordings
Administrator > Audit > Web Apps > User Activity Recordings
@@ -31,7 +31,7 @@ Administrator > Audit > Web Apps > User Activity Recordings 7. **Client Ip** : クライアントIPアドレス 4. 検索フィールド右側フィルターボタンをクリックしてAND条件で以下のフィルタリングが可能です。
- ![image-20250629-175600.png](/administrator-manual/audit/web-app-logs/user-activity-recordings/image-20250629-175600.png) + image-20250629-175600.png
**a. Action At** : アクション発生日時範囲 @@ -42,7 +42,7 @@ Administrator > Audit > Web Apps > User Activity Recordings 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Web Apps > User Activity Recordings > User Activity Recordings Details](/administrator-manual/audit/web-app-logs/user-activity-recordings/image-20250629-175637.png) +Administrator > Audit > Web Apps > User Activity Recordings > User Activity Recordings Details
Administrator > Audit > Web Apps > User Activity Recordings > User Activity Recordings Details
diff --git a/src/content/ja/administrator-manual/audit/web-app-logs/web-access-history.mdx b/src/content/ja/administrator-manual/audit/web-app-logs/web-access-history.mdx index d2440c8e..679308b7 100644 --- a/src/content/ja/administrator-manual/audit/web-app-logs/web-access-history.mdx +++ b/src/content/ja/administrator-manual/audit/web-app-logs/web-access-history.mdx @@ -11,7 +11,7 @@ title: 'Web Access History' ### Web Access Historyの照会
-![Administrator > Audit > Web Apps > Web Access History](/administrator-manual/audit/web-app-logs/web-access-history/image-20250629-171743.png) +Administrator > Audit > Web Apps > Web Access History
Administrator > Audit > Web Apps > Web Access History
@@ -31,7 +31,7 @@ Administrator > Audit > Web Apps > Web Access History 9. **Message** : メッセージ内容 4. 検索フィールド右側フィルターボタンをクリックしてAND条件で以下のフィルタリングが可能です。
- ![image-20250629-171829.png](/administrator-manual/audit/web-app-logs/web-access-history/image-20250629-171829.png) + image-20250629-171829.png
1. **Action Type** : アクションタイプ 2. **Action At** : アクション発生日時範囲 @@ -41,7 +41,7 @@ Administrator > Audit > Web Apps > Web Access History 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Web Apps > Web Access History > Web Access History Details](/administrator-manual/audit/web-app-logs/web-access-history/image-20250629-172248.png) +Administrator > Audit > Web Apps > Web Access History > Web Access History Details
Administrator > Audit > Web Apps > Web Access History > Web Access History Details
diff --git a/src/content/ja/administrator-manual/audit/web-app-logs/web-app-role-history.mdx b/src/content/ja/administrator-manual/audit/web-app-logs/web-app-role-history.mdx index 9def4972..f33e9c76 100644 --- a/src/content/ja/administrator-manual/audit/web-app-logs/web-app-role-history.mdx +++ b/src/content/ja/administrator-manual/audit/web-app-logs/web-app-role-history.mdx @@ -11,7 +11,7 @@ title: 'Web App Role History' ### Web App Role Historyの照会
-![Administrator > Audit > Web Apps > Web App Role History](/administrator-manual/audit/web-app-logs/web-app-role-history/Screenshot-2025-06-30-at-2.47.18-PM.png) +Administrator > Audit > Web Apps > Web App Role History
Administrator > Audit > Web Apps > Web App Role History
@@ -22,7 +22,7 @@ Administrator > Audit > Web Apps > Web App Role History 3. テーブル左上の検索欄を通じて以下の条件で検索が可能です。
a. User Name : ユーザー名
b. User Email : ユーザーメール
c. Role Name : 役割名 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![Screenshot-2025-06-30-at-2.48.27-PM.png](/administrator-manual/audit/web-app-logs/web-app-role-history/Screenshot-2025-06-30-at-2.48.27-PM.png) + Screenshot-2025-06-30-at-2.48.27-PM.png
1. **Event** : イベントタイプ 2. **User Type** : ユーザータイプ @@ -44,7 +44,7 @@ Administrator > Audit > Web Apps > Web App Role History 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Web Apps > Web App Role History > Web App Role History Details](/administrator-manual/audit/web-app-logs/web-app-role-history/Screenshot-2025-06-30-at-2.50.17-PM.png) +Administrator > Audit > Web Apps > Web App Role History > Web App Role History Details
Administrator > Audit > Web Apps > Web App Role History > Web App Role History Details
diff --git a/src/content/ja/administrator-manual/audit/web-app-logs/web-event-audit.mdx b/src/content/ja/administrator-manual/audit/web-app-logs/web-event-audit.mdx index 322f5e9f..08d24cad 100644 --- a/src/content/ja/administrator-manual/audit/web-app-logs/web-event-audit.mdx +++ b/src/content/ja/administrator-manual/audit/web-app-logs/web-event-audit.mdx @@ -12,7 +12,7 @@ title: 'Web Event Audit' ### Web Event Auditの照会
-![Administrator > Audit > Web Apps > Web Event Audit](/administrator-manual/audit/web-app-logs/web-event-audit/image-20250629-172952.png) +Administrator > Audit > Web Apps > Web Event Audit
Administrator > Audit > Web Apps > Web Event Audit
@@ -33,7 +33,7 @@ Administrator > Audit > Web Apps > Web Event Audit 10. Message : メッセージ内容 4. 検索フィールド右側フィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20250629-173418.png](/administrator-manual/audit/web-app-logs/web-event-audit/image-20250629-173418.png) + image-20250629-173418.png
1. Event Type : イベントタイプ（Mouse Clicked/Clipboard Copiedなど） 2. Result : 実行結果（Success/Failure） @@ -57,7 +57,7 @@ Administrator > Audit > Web Apps > Web Event Audit 各行をクリックすると詳細情報照会が可能です。
-![Administrator > Audit > Web Apps > Web Event Audit > Event Audit Detail](/administrator-manual/audit/web-app-logs/web-event-audit/image-20250629-172959.png) +Administrator > Audit > Web Apps > Web Event Audit > Event Audit Detail
Administrator > Audit > Web Apps > Web Event Audit > Event Audit Detail
diff --git a/src/content/ja/administrator-manual/databases.mdx b/src/content/ja/administrator-manual/databases.mdx index be3d9e45..f849c800 100644 --- a/src/content/ja/administrator-manual/databases.mdx +++ b/src/content/ja/administrator-manual/databases.mdx @@ -7,7 +7,7 @@ import { Callout } from 'nextra/components' # Databases
-![screenshot-20240523-193355.png](/administrator-manual/databases/screenshot-20240523-193355.png) +screenshot-20240523-193355.png
### Overview diff --git a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers.mdx b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers.mdx index 4e2f276b..5f2fcf50 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' QueryPieではクラウド提供者に登録されたDBリソースを連動し、定期的に同期できます。
-![Administrator > Databases > Connection Management > Cloud Providers](/administrator-manual/databases/connection-management/cloud-providers/image-20240714-055708.png) +Administrator > Databases > Connection Management > Cloud Providers
Administrator > Databases > Connection Management > Cloud Providers
@@ -43,7 +43,7 @@ Administrator > Databases > Connection Management > Cloud Providers ### Cloud Providerの削除
-![image-20241103-065154.png](/administrator-manual/databases/connection-management/cloud-providers/image-20241103-065154.png) +image-20241103-065154.png
1. Administrator > Databases > Connection Management > Cloud Providersメニューに移動します。 @@ -65,7 +65,7 @@ Cloud Provider削除時、該当クラウドプロバイダーを通じて同期
-![image-20241101-001430.png](/administrator-manual/databases/connection-management/cloud-providers/image-20241101-001430.png) +image-20241101-001430.png
1. Databases > [Connection Management] > Cloud Providerの一覧で特定プロバイダー項目を選択します。 diff --git a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx index b6c3c744..5cbd9e40 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws.mdx @@ -19,7 +19,7 @@ AWS内のリソースを同期してQueryPieで管理するデータベースと
-![Administrator > Databases > Connection Management > Cloud Providers](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20241217-084317.png) +Administrator > Databases > Connection Management > Cloud Providers
Administrator > Databases > Connection Management > Cloud Providers
@@ -50,7 +50,7 @@ Administrator > Databases > Connection Management > Cloud Providers ### Credentialタイプ別認証方式設定
-![Administrator > Databases > Connection Management > Cloud Provider > Create Provider](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20240725-043642.png) +Administrator > Databases > Connection Management > Cloud Provider > Create Provider
Administrator > Databases > Connection Management > Cloud Provider > Create Provider
@@ -65,7 +65,7 @@ Administrator > Databases > Connection Management > Cloud Provider > **Save Credential for Synchronizationオプション**
-![Save Credential for Synchronization](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20241220-095857.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -91,7 +91,7 @@ Save Credential for Synchronization
-![Administrator > Databases > Connection Management > Cloud Providers > Details](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-aws/image-20241220-100746.png) +Administrator > Databases > Connection Management > Cloud Providers > Details
Administrator > Databases > Connection Management > Cloud Providers > Details
diff --git a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx index 12a35ce6..244212ac 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud.mdx @@ -18,7 +18,7 @@ GCP内のリソースを同期してQueryPieで管理するデータベースと
-![Administrator > Databases > Connection Management > Cloud Providers](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud/image-20241217-123654.png) +Administrator > Databases > Connection Management > Cloud Providers
Administrator > Databases > Connection Management > Cloud Providers
@@ -48,7 +48,7 @@ Administrator > Databases > Connection Management > Cloud Providers **Save Credential for Synchronizationオプション**
-![Save Credential for Synchronization](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud/image-20241220-094727.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -62,7 +62,7 @@ Save Credential for Synchronization ### 登録されたGCP Cloud Provider同期および管理
-![Administrator > Databases > Connection Management > Cloud Providers > Details](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-google-cloud/image-20241220-095231.png) +Administrator > Databases > Connection Management > Cloud Providers > Details
Administrator > Databases > Connection Management > Cloud Providers > Details
diff --git a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx index 1523fc2f..6276940d 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure.mdx @@ -19,7 +19,7 @@ Azure内のリソースを同期してQueryPieで管理するデータベース
-![Administrator > Databases > Connection Management > Cloud Providers > Create Provider](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure/image-20241217-102747.png) +Administrator > Databases > Connection Management > Cloud Providers > Create Provider
Administrator > Databases > Connection Management > Cloud Providers > Create Provider
@@ -53,7 +53,7 @@ Administrator > Databases > Connection Management > Cloud Providers > **Save Credential for Synchronizationオプション**
-![Save Credential for Synchronization](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure/image-20241221-025943.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -68,7 +68,7 @@ Save Credential for Synchronization ### 登録されたAzure Cloud Provider同期および管理
-![Administrator > Databases > Connection Management > Cloud Providers > Details](/administrator-manual/databases/connection-management/cloud-providers/synchronizing-db-resources-from-ms-azure/image-20241219-060152.png) +Administrator > Databases > Connection Management > Cloud Providers > Details
Administrator > Databases > Connection Management > Cloud Providers > Details
diff --git a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx index 317ba2f5..445967c1 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature.mdx @@ -15,12 +15,12 @@ title: 'Dry Run機能でクラウド同期設定確認' 2. 詳細ページで変更したい設定項目を変更した後、右上の`Dry Run`ボタンをクリックします。
-![image-20241101-001430.png](/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature/image-20241101-001430.png) +image-20241101-001430.png
1. ポップアップ窓に出力される「Dry Run」結果を確認し、もし問題があれば入力した内容を修正します。問題がなければ`Save Changes`ボタンを押して変更事項を保存します。

- ![image-20241101-002631.png](/administrator-manual/databases/connection-management/cloud-providers/verifying-cloud-synchronization-settings-with-dry-run-feature/image-20241101-002631.png) + image-20241101-002631.png
diff --git a/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx b/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx index 555affc0..6d1d5a83 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/db-connections.mdx @@ -18,7 +18,7 @@ DB ConnectionsページでQueryPieに登録されているDBコネクション DB Connectionsページ右上の`Create Connection`ボタンをクリックして手動登録ページに進入します。
-![Administrator> Databases> Connection Management> DB Connections> Create Connection> Click here](/administrator-manual/databases/connection-management/db-connections/Screenshot-2025-04-10-at-11.33.36-AM.png) +Administrator> Databases> Connection Management> DB Connections> Create Connection> Click here
Administrator> Databases> Connection Management> DB Connections> Create Connection> Click here
@@ -29,7 +29,7 @@ Administrator> Databases> Connection Management> DB Connections> Cre このモーダルは主要機能項目（Web Editor、Access Control、Audit Log、Privilege Control、Data Policy、Proxy、DML Snapshot、Ledger Management）で構成されており、各ベンダー別にサポート有無を直感的に確認できるよう助けます。
-![Administrator > Databases > Connection Management > DB Connections > Create Connection](/administrator-manual/databases/connection-management/db-connections/image-20240725-062325.png) +Administrator > Databases > Connection Management > DB Connections > Create Connection
Administrator > Databases > Connection Management > DB Connections > Create Connection
@@ -64,7 +64,7 @@ Administrator > Databases > Connection Management > DB Connections > Cloud Providerを通じてリソースを同期する場合、リソースがクラスターで構成されているとClusterモードが有効化されます。
-![Administrator > Databases > Connection Management > DB Connections > List Details](/administrator-manual/databases/connection-management/db-connections/image-20240725-062536.png) +Administrator > Databases > Connection Management > DB Connections > List Details
Administrator > Databases > Connection Management > DB Connections > List Details
@@ -96,7 +96,7 @@ Clusterモード活用時クラスターおよびインスタンスエンドポ 管理者コンソール内Databases設定 > DB Connectionsページで現在QueryPieに登録されたDBコネクションリストを確認できます。
-![Administrator > Databases > Connection Management > DB Connections](/administrator-manual/databases/connection-management/db-connections/image-20240714-055800.png) +Administrator > Databases > Connection Management > DB Connections
Administrator > Databases > Connection Management > DB Connections
@@ -109,7 +109,7 @@ Administrator > Databases > Connection Management > DB Connections * **Favorite View** ：お気に入り設定有無 * テーブル最も右側にお気に入り設定のためのボタンがあります。
- ![お気に入り設定ボタン](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-222905.png) + お気に入り設定ボタン
お気に入り設定ボタン
@@ -128,7 +128,7 @@ Administrator > Databases > Connection Management > DB Connections DB Connectionsページで詳細情報を照会しようとするアイテムをクリックすると詳細ページに進入します。
-![Administrator > Databases > Connection Management > DB Connections > List Details](/administrator-manual/databases/connection-management/db-connections/Screenshot-2025-04-10-at-11.37.08-AM.png) +Administrator > Databases > Connection Management > DB Connections > List Details
Administrator > Databases > Connection Management > DB Connections > List Details
@@ -141,7 +141,7 @@ Administrator > Databases > Connection Management > DB Connections > DBコネクション詳細ページ右上`Accessible Users`ボタンをクリックするとDrawerが開き、該当コネクションにアクセス可能なユーザーリストを照会できます。
-![Administrator > Databases > DB Connections > List Details > Accessible Users](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-223340.png) +Administrator > Databases > DB Connections > List Details > Accessible Users
Administrator > Databases > DB Connections > List Details > Accessible Users
@@ -152,7 +152,7 @@ Administrator > Databases > DB Connections > List Details > Accessib DBコネクション詳細ページ内Connection Information領域で生成時入力した情報を照会し修正できます。
-![Administrator > Databases > DB Connections > List Details > Connection Information](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-223248.png) +Administrator > Databases > DB Connections > List Details > Connection Information
Administrator > Databases > DB Connections > List Details > Connection Information
@@ -203,7 +203,7 @@ Secret Store設定に保存されたSecret Engineタイプに 따라DB Account 該当DBコネクションに適用される詳細ポリシーを入力します。`Save Changes`ボタンで保存します。
-![Additional Informationタブ](/administrator-manual/databases/connection-management/db-connections/image-20250825-005925.png) +Additional Informationタブ
Additional Informationタブ
@@ -237,7 +237,7 @@ Additional Informationタブ * 3rd party tool（DBeaver、DataGripなど）を使用する時理由入力を強制できるのはSQL Execute項目のみ該当します。 * 3rd party toolで内部的に送信するクエリ（DBスキーマをツリー構造で見せたりデータタイプをUIで表示してくれる機能を実行するクエリ）もSQL Executeで検出されて理由入力を要求します。例）最初接続した直後クエリを入力しなかったにもかかわらず理由入力ウィンドウがポップアップされます。この場合SQL構文の種類を判断しないため設定に応じて相当不便を招く可能性があります。したがってDatabase > General > ConfigurationsのQuery Purpose Duration for Agentオプションの値を適切に調節しなければなりません。
- ![image-20250825-020520.png](/administrator-manual/databases/connection-management/db-connections/image-20250825-020520.png) + image-20250825-020520.png
@@ -247,7 +247,7 @@ Additional Informationタブ Proxy Usageを有効化すると以下のように2つの選択事項が表示されます。
-![Proxy Usageのオプション](/administrator-manual/databases/connection-management/db-connections/image-20241222-134235.png) +Proxy Usageのオプション
Proxy Usageのオプション
@@ -266,7 +266,7 @@ QueryPie 10.2.2から乱数パスワード使用が困難な状況に対する チェックボックスを通じてSSLまたはSSH使用有無を有効化し、下部ドロップダウンで既登録された設定情報を選択します。`Save Changes`ボタンで保存します。
-![SSL/SSH Settingタブ](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-180833.png) +SSL/SSH Settingタブ
SSL/SSH Settingタブ
@@ -285,7 +285,7 @@ Connection Ownerタブで`Add Connection Owner`ボタンをクリックし、DB （ユーザーまたはグループ単位で指定可能）`Save Changes`ボタンで保存します。
-![Connection Ownerタブ](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-180851.png) +Connection Ownerタブ
Connection Ownerタブ
@@ -301,7 +301,7 @@ TagsタブでDBコネクション別にタグを登録して管理できます 入力完了後`Save Changes`ボタンで保存します。
-![Tagsタブ](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-231618.png) +Tagsタブ
Tagsタブ
@@ -317,7 +317,7 @@ DBコネクションにPrivilege別に使用しなければならない接続ア
-![Privilege Settingタブ](/administrator-manual/databases/connection-management/db-connections/screenshot-20240726-154730.png) +Privilege Settingタブ
Privilege Settingタブ
@@ -332,7 +332,7 @@ BigQuery、Dynamo、Athena、Impala、Presto、Trino、RedisベンダーはPrivi
-![QueryPie Web > Databases > Connections](/administrator-manual/databases/connection-management/db-connections/screenshot-20240730-231958.png) +QueryPie Web > Databases > Connections
QueryPie Web > Databases > Connections
@@ -345,7 +345,7 @@ QueryPie Web > Databases > Connections 11.3.0でAdvanced privilege設定時、特権アカウントに対してパスワードを登録しない場合、特権アカウント（管理者アカウント）が対象に接続する際に手動でパスワードを入力できるよう変更されました。
-![image-20251013-050034.png](/administrator-manual/databases/connection-management/db-connections/image-20251013-050034.png) +image-20251013-050034.png
Advanced privilege設定時、手動でDBアカウントのパスワードを入力するようにするには、上図のようにPassword欄を空白にしてHide this credential from connection list pageチェックボックスを解除状態に設定する必要があります。 diff --git a/src/content/ja/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx b/src/content/ja/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx index 1472d2b2..36ac2088 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide.mdx @@ -13,7 +13,7 @@ title: 'AWS Athena専用ガイド' AWS IAM > Usersページで確認できます。
-![Screenshot-2025-01-23-at-7.20.29-PM.png](/administrator-manual/databases/connection-management/db-connections/aws-athena-specific-guide/Screenshot-2025-01-23-at-7.20.29-PM.png) +Screenshot-2025-01-23-at-7.20.29-PM.png
### Cloud Provider diff --git a/src/content/ja/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx b/src/content/ja/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx index 297e7037..2827f862 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification.mdx @@ -30,19 +30,19 @@ Custom Data SourceはQueryPieで基本的にサポートしないベンダーに * Admin > Databases > Connection Management > DB Connectionsを選択します。 * `+ Create Connection`ボタンをクリックします。
- ![Screenshot-2025-03-05-at-10.10.11-AM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-10.10.11-AM.png) + Screenshot-2025-03-05-at-10.10.11-AM.png
2. **Custom Data Source作成** * Custom Data Sourceアイコンをクリックします。
- ![Screenshot-2025-03-05-at-10.11.42-AM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-10.11.42-AM.png) + Screenshot-2025-03-05-at-10.11.42-AM.png
* 作成時に以下のような警告メッセージが表示されます:
**Restrictions:** * Only TCP access control is available; Privileges controland Query Audit are not supported. * Access is only possible through a proxy; it cannot be accessed via the web editor. * 以下の接続情報を希望する設定に合わせて入力します。 ****
- ![Screenshot-2025-03-05-at-12.02.22-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-12.02.22-PM.png) + Screenshot-2025-03-05-at-12.02.22-PM.png
* Connection Name（必須）: 接続名入力 * Host（必須）: 対象データソースのホストアドレス @@ -61,13 +61,13 @@ Custom Data SourceはQueryPieで基本的にサポートしないベンダーに * 希望する項目を変更でき、Tagを追加できます。 * 修正後、右上の`Save Changes`ボタンをクリックして変更事項を保存します。
- ![Screenshot-2025-03-05-at-6.43.08-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-6.43.08-PM.png) + Screenshot-2025-03-05-at-6.43.08-PM.png
* **削除** * DB Connections一覧で削除を希望するコネクションの左側チェックボックスを選択後`Delete`ボタンをクリックします。 * "Are you sure you want to delete"文句が出た後`OK`ボタンをクリックしてコネクションを削除します。
- ![Screenshot-2025-03-05-at-6.54.56-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-6.54.56-PM.png) + Screenshot-2025-03-05-at-6.54.56-PM.png
#### Access Control設定 @@ -82,7 +82,7 @@ Custom Data SourceはQueryPieで基本的にサポートしないベンダーに * 付与時、期限日（Expiration Date）を設定できます。 * 選択完了後`Grant`ボタンを押して権限を付与します。
- ![Screenshot-2025-03-05-at-1.59.53-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-1.59.53-PM.png) + Screenshot-2025-03-05-at-1.59.53-PM.png
@@ -92,7 +92,7 @@ Custom Data SourceはQueryPieで基本的にサポートしないベンダーに * Admin > Databases > DB Access Control > Access Control > Userを選択します。 * Detailページで権限を回収するためのコネクションを選択した後`Revoke`ボタンをクリックします。
- ![Screenshot-2025-03-05-at-3.18.12-PM.png](/administrator-manual/databases/connection-management/db-connections/custom-data-source-configuration-and-log-verification/Screenshot-2025-03-05-at-3.18.12-PM.png) + Screenshot-2025-03-05-at-3.18.12-PM.png
#### Audit Log確認 diff --git a/src/content/ja/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx b/src/content/ja/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx index 1dee6e1b..7f729676 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide.mdx @@ -19,7 +19,7 @@ Amazon DocumentDB専用詳細設定ガイドをここで提供します。 インスタンスendpointで接続するよりCluster endpointを使用することをお勧めします。
-![image-20240122-102557.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240122-102557.png) +image-20240122-102557.png
### Amazon DocumentDB TLS（SSL）使用 @@ -36,7 +36,7 @@ AWSではリージョンに関係なく共同で使用できる[globalバンド 2. QueryPie管理者コンソールでDatabases > Connection Management > SSL Configurationsメニューに移動します。
-![image-20240730-112808.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240730-112808.png) +image-20240730-112808.png
1. 右上にある`Create SSL`ボタンを押します。 @@ -46,7 +46,7 @@ AWSではリージョンに関係なく共同で使用できる[globalバンド 5. `Save`ボタンを押して設定を保存します。
-![image-20240220-225433.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240220-225433.png) +image-20240220-225433.png
#### DocumentDBに認証書マッピング @@ -57,7 +57,7 @@ AWSではリージョンに関係なく共同で使用できる[globalバンド 4. `Use SSL`チェックボックスをチェックしてアクティブにした後**SSL Configurations**で前段階（CAバンドル認証書登録）で登録した設定名を選択します。
-![image-20240220-230604.png](/administrator-manual/databases/connection-management/db-connections/documentdb-specific-guide/image-20240220-230604.png) +image-20240220-230604.png
1. 右上の`Save Changes`ボタンを押して設定を保存します。 diff --git a/src/content/ja/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx b/src/content/ja/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx index 2406bac2..33b2196a 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration.mdx @@ -20,7 +20,7 @@ Google Cloud API Integration設定方法はこの文書を参照してくださ クラウド同期を通じて生成されたコネクションや手動で作ったコネクションすべてAuthentication Methodを"Using Google User Account (OAuth 2.0)"で選択できます。
-![新しいBigQueryコネクションを作成する時にAuthentication Method指定](/administrator-manual/databases/connection-management/db-connections/google-bigquery-oauth-authentication-configuration/image-20250116-112226.png) +新しいBigQueryコネクションを作成する時にAuthentication Method指定
新しいBigQueryコネクションを作成する時にAuthentication Method指定
diff --git a/src/content/ja/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx b/src/content/ja/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx index 58f58d06..51c8ea06 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide.mdx @@ -54,7 +54,7 @@ mongodb+srv:///?[options] #### 2. MongoDBコネクション作成
-![Administrator > Databases > Connection Management > DB Connections > Create Connection](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-113638.png) +Administrator > Databases > Connection Management > DB Connections > Create Connection
Administrator > Databases > Connection Management > DB Connections > Create Connection
@@ -69,7 +69,7 @@ Administrator > Databases > Connection Management > DB Connections > ##### < Standard Connection >
-![image-20240730-114050.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114050.png) +image-20240730-114050.png
1. Allowed Zoneに適切なネットワークzone設定をします。 @@ -86,7 +86,7 @@ Administrator > Databases > Connection Management > DB Connections > 3. Exposeはコネクション情報での個別インスタンスの露出可否を決定できるオプションです。
**マルチホスト機能を使用するには必ずインスタンスがexpose状態でなければならないため、必ず**`Expose`**オプションをアクティブにします。**
-![image-20240730-114226.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114226.png) +image-20240730-114226.png
1. Authentication DB : Authentication DB（authSource）の値を入力します。 @@ -104,7 +104,7 @@ ______ ##### < +srv Connection >
-![image-20240730-114540.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114540.png) +image-20240730-114540.png
1. Allowed Zoneに適切なネットワークzone設定をします。 @@ -130,7 +130,7 @@ Sharded ClusterはReplica SetとConnection Stringのオプションのみ異な Replica Setは replicaSet=[replica set name] オプションが必要ですが、Sharded Clusterはこのオプションが不要です。
-![image-20240730-114833.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-114833.png) +image-20240730-114833.png
##### < Standard Connection > @@ -168,7 +168,7 @@ Clusterモードに対するより詳細な内容は[DB Connections](.)でも確 Proxyを使用する場合、DataGripなどのSQL ClientでTLS設定と別にQueryPieでもSSL設定が必要です。
[SSL Configurations](../ssl-configurations)を参照して設定後、コネクションのSSL設定に反映する必要があります。
-![image-20240731-050745.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240731-050745.png) +image-20240731-050745.png
@@ -189,7 +189,7 @@ QueryPieでサポートするDBMS中MongoDBの場合は常にデータをJSON形 #### マスキング政策に規則登録
-![Administrator > Databases > Policies > Data Masking > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-115120.png) +Administrator > Databases > Policies > Data Masking > Add Rule List
Administrator > Databases > Policies > Data Masking > Add Rule List
@@ -215,7 +215,7 @@ Administrator > Databases > Policies > Data Masking > Add Rule List 政策を作成した後、実際に政策を適用するデータのパスを規則として登録します。
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-115402.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
@@ -254,7 +254,7 @@ Rule Listタブで規則が登録されたことを確認できます。 ##### Case 1. item属性アクセス制限
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-115402.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
@@ -263,7 +263,7 @@ Administrator > Databases > Policies > Data Access > Add Rule List 1つの属性に対してアクセス制限政策を設定する場合、「Column Name」項目に該当するitemを入力後`OK`ボタンをクリックします。
-![image-20240730-120312.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120312.png) +image-20240730-120312.png
上スクリーンショットのようにitem（"T_PWD"）属性の値が"Restricted Column"で表示されることを確認できます。 @@ -273,14 +273,14 @@ Administrator > Databases > Policies > Data Access > Add Rule List size下位のh属性に対してアクセス制限政策を設定する場合、「Column Name」項目に`$.size.h`を入力後`OK`ボタンをクリックします。
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120011.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
-![image-20240730-120215.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120215.png) +image-20240730-120215.png
上スクリーンショットのようにsize下位のh属性の値が"Restricted Column"で表示されることを確認できます。 @@ -290,14 +290,14 @@ Administrator > Databases > Policies > Data Access > Add Rule List size下位のすべての属性に対してアクセス制限政策を設定する場合、「Column Name」項目に`$.size`を入力後`OK`ボタンをクリックします。
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120351.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
-![image-20240730-120421.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120421.png) +image-20240730-120421.png
上スクリーンショットのようにsize下位のすべての属性の値が"Restricted Column"で表示されることを確認できます。 @@ -307,14 +307,14 @@ Administrator > Databases > Policies > Data Access > Add Rule List tags属性のリスト値中2番目の値に対するアクセス制限政策を設定する場合、「Column Name」項目に`$.tags[1]`を入力後`OK`ボタンをクリックします。
-![Administrator > Databases > Policies > Data Access > Add Rule List](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120507.png) +Administrator > Databases > Policies > Data Access > Add Rule List
Administrator > Databases > Policies > Data Access > Add Rule List
-![image-20240730-120544.png](/administrator-manual/databases/connection-management/db-connections/mongodb-specific-guide/image-20240730-120544.png) +image-20240730-120544.png
上スクリーンショットのようにtags属性の2番目の値が"Restricted Column"で表示されることを確認できます。 diff --git a/src/content/ja/administrator-manual/databases/connection-management/kerberos-configurations.mdx b/src/content/ja/administrator-manual/databases/connection-management/kerberos-configurations.mdx index c03f224e..53a59005 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/kerberos-configurations.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/kerberos-configurations.mdx @@ -15,7 +15,7 @@ Kerberos Configurationsページ右上`Create Keytab`ボタンをクリックし キータブファイルをアップロードし、Kerberos構成の名前を入力した後`Save`ボタンをクリックして保存します。
-![Administrator > Databases > Connection Management > Kerberos Configurations > Create Keytab](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111247.png) +Administrator > Databases > Connection Management > Kerberos Configurations > Create Keytab
Administrator > Databases > Connection Management > Kerberos Configurations > Create Keytab
@@ -27,7 +27,7 @@ Administrator > Databases > Connection Management > Kerberos Configurat Kerberos Configurationsページで登録されたキータブ一覧を照会できます。
-![Administrator > Databases > Connection Management > Kerberos Configurations](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111157.png) +Administrator > Databases > Connection Management > Kerberos Configurations
Administrator > Databases > Connection Management > Kerberos Configurations
@@ -40,7 +40,7 @@ Kerberos Configurationsページ内一覧で削除したいアイテムをチェ ボタンをクリックし、確認モーダルで`Delete`ボタンをクリックすると削除が完了します。
-![Administrator > Databases > Connection Management > Kerberos Configurations > Delete Keytab](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111214.png) +Administrator > Databases > Connection Management > Kerberos Configurations > Delete Keytab
Administrator > Databases > Connection Management > Kerberos Configurations > Delete Keytab
@@ -53,7 +53,7 @@ Kerberos Configurationsページ右上`⚙️`ボタンをクリックしてQuer 変更内容を保存するには`Save`ボタンをクリックしてください。
-![Administrator > Databases > Connection Management > Kerberos Configurations > Kerberos Configuration Setting](/administrator-manual/databases/connection-management/kerberos-configurations/screenshot-20240731-111234.png) +Administrator > Databases > Connection Management > Kerberos Configurations > Kerberos Configuration Setting
Administrator > Databases > Connection Management > Kerberos Configurations > Kerberos Configuration Setting
diff --git a/src/content/ja/administrator-manual/databases/connection-management/ssh-configurations.mdx b/src/content/ja/administrator-manual/databases/connection-management/ssh-configurations.mdx index b3fe0732..dfd7df37 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/ssh-configurations.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/ssh-configurations.mdx @@ -9,7 +9,7 @@ title: 'SSH Configurations' SSH ConfigurationsはDBコネクション接続時に使用するSSHトンネリング情報を管理するページです。
-![Administrator > Databases > Connection Management > SSH Configuration > Create SSH Configuration](/administrator-manual/databases/connection-management/ssh-configurations/screenshot-20240730-230232.png) +Administrator > Databases > Connection Management > SSH Configuration > Create SSH Configuration
Administrator > Databases > Connection Management > SSH Configuration > Create SSH Configuration
diff --git a/src/content/ja/administrator-manual/databases/connection-management/ssl-configurations.mdx b/src/content/ja/administrator-manual/databases/connection-management/ssl-configurations.mdx index 4c4dca37..67a33cbf 100644 --- a/src/content/ja/administrator-manual/databases/connection-management/ssl-configurations.mdx +++ b/src/content/ja/administrator-manual/databases/connection-management/ssl-configurations.mdx @@ -9,7 +9,7 @@ title: 'SSL Configurations' SSL ConfigurationsページでDBコネクションに接続する際に使用するSSL構成情報を登録します。
-![Administrator > Databases > Connection Management > SSL Configuration > Create SSL](/administrator-manual/databases/connection-management/ssl-configurations/screenshot-20240730-230107.png) +Administrator > Databases > Connection Management > SSL Configuration > Create SSL
Administrator > Databases > Connection Management > SSL Configuration > Create SSL
diff --git a/src/content/ja/administrator-manual/databases/dac-general-configurations.mdx b/src/content/ja/administrator-manual/databases/dac-general-configurations.mdx index 15771bfe..9959b433 100644 --- a/src/content/ja/administrator-manual/databases/dac-general-configurations.mdx +++ b/src/content/ja/administrator-manual/databases/dac-general-configurations.mdx @@ -19,7 +19,7 @@ import { Callout } from 'nextra/components' DBアクセス制御に適用される設定を管理します。
-![image-20251218-083844.png](/administrator-manual/databases/dac-general-configurations/image-20251218-083844.png) +image-20251218-083844.png
@@ -29,10 +29,10 @@ DBアクセス制御に適用される設定を管理します。
基本的にクエリ共有設定はオフになっており、`Query Sharing Setting`ボタンをクリックすると設定モーダルがポップアップします。 Query SharingオプションをOnに選択すると、追加入力項目が表示されます。
-![screenshot-20240726-145003.png](/administrator-manual/databases/dac-general-configurations/screenshot-20240726-145003.png) +screenshot-20240726-145003.png
-![screenshot-20240726-145650.png](/administrator-manual/databases/dac-general-configurations/screenshot-20240726-145650.png) +screenshot-20240726-145650.png
* **Git Repository URL** : クエリを送信するGit Repository URL @@ -76,12 +76,12 @@ ______ * DB Access Requestリクエスト時に指定された期間を超過した期限日設定不可 * **Notification of Access Expiration** : ユーザーの権限期限切れ（Privilege Expiration、Policy Exception Expiration）前にメールで事前通知を受けることができます。
- ![image-20251218-084512.png](/administrator-manual/databases/dac-general-configurations/image-20251218-084512.png) + image-20251218-084512.png
* **Display the first 10 rows in Query Audit** : Query Audit内SELECT文実行結果の表示方式設定（Default : OffでOnに設定した場合、全体結果を表示せず、最初の10行のみ表示されます）
-![Query Audit Detail](/administrator-manual/databases/dac-general-configurations/screenshot-20231210-174400.png) +Query Audit Detail
Query Audit Detail
@@ -98,7 +98,7 @@ Query Audit Detail * Allowed User : 該当構文実行を許可するユーザー指定（複数選択可能、グループ単位指定不可） * 入力されたRestricted Statementを含むクエリ実行時ブロックされる
- ![image-20240326-011036.png](/administrator-manual/databases/dac-general-configurations/image-20240326-011036.png) + image-20240326-011036.png
@@ -109,7 +109,7 @@ Restricted StatementポリシーによってブロックされるクエリはSQL * **Justification Length** : Connection設定で「User Action Purpose Required」オプションが有効化されているか、Ledger table managementポリシーで理由入力を強制した場合、Web EditorまたはAgentを通じて理由入力をする必要があります。この時、入力欄に入力する文字長の最小値および最大値を管理者が指定します。 * 入力値の最小値は1で最大値は1000です。
- ![image-20250824-233845.png](/administrator-manual/databases/dac-general-configurations/image-20250824-233845.png) + image-20250824-233845.png
* **Query Annotation** : クエリ実行時に自動で管理者が指定したコメントを記録します。機能を有効化した場合、以下の3つのテンプレートを使用してコメントを記録します。10.4.0基準Redshift限定サポート。 * User Name: `{{userName}}` : クエリを実行したユーザーのDisplay Nameです。 @@ -117,7 +117,7 @@ Restricted StatementポリシーによってブロックされるクエリはSQL * Execute From: `{{executedFrom}}` : クエリを実行した手段です。10.4.0基準Web Editorのみ記録されます。
-![Query Audit](/administrator-manual/databases/dac-general-configurations/image-20250627-140103.png) +Query Audit
Query Audit
@@ -128,7 +128,7 @@ Query Audit * **Member based Connection Filtering :** WorkflowでDB Access Requestフォームで特定ユーザーまたはグループに対して全体コネクションを表示せず、指定したコネクションのみ表示するようフィルタリングする機能です。 * コネクションの詳細画面でconnection memberに登録されたユーザー/グループのみ該当コネクションがWorkflow DB Access Reqeustに表示されます。
- ![Databases > Connection Management > DB Connections の特定コネクション詳細画面でConnection Memberに特定ユーザーまたはグループを割り当て](/administrator-manual/databases/dac-general-configurations/image-20250627-141133.png) + Databases > Connection Management > DB Connections の特定コネクション詳細画面でConnection Memberに特定ユーザーまたはグループを割り当て
Databases > Connection Management > DB Connections の特定コネクション詳細画面でConnection Memberに特定ユーザーまたはグループを割り当て
@@ -146,7 +146,7 @@ Query Audit * 最小値 : 1時間
-![image-20251009-150744.png](/administrator-manual/databases/dac-general-configurations/image-20251009-150744.png) +image-20251009-150744.png
diff --git a/src/content/ja/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx b/src/content/ja/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx index 246661e3..c37c3077 100644 --- a/src/content/ja/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx +++ b/src/content/ja/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated.mdx @@ -22,7 +22,7 @@ Masing Patternページで登録されたマスキングパターンを照会で （パターン名で検索可能）
-![Administrator > Databases > General > Masking Pattern](/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated/image-20250826-005621.png) +Administrator > Databases > General > Masking Pattern
Administrator > Databases > General > Masking Pattern
@@ -34,7 +34,7 @@ Administrator > Databases > General > Masking Pattern テーブルで詳細情報を照会したいアイテムをクリックするとDrawerが開き、詳細情報を照会、変更、または削除できます。
-![Administrator > Databases > General > Masking Pattern > Details](/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated/image-20250826-005930.png) +Administrator > Databases > General > Masking Pattern > Details
Administrator > Databases > General > Masking Pattern > Details
@@ -60,7 +60,7 @@ Administrator > Databases > General > Masking Pattern > Details 必要な情報をすべて入力後`Save`ボタンを押して保存します。
-![Create Pattern](/administrator-manual/databases/dac-general-configurations/masking-pattern-menu-relocated/screenshot-20240731-174002.png) +Create Pattern
Create Pattern
diff --git a/src/content/ja/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx b/src/content/ja/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx index 74f1205d..6e777f9e 100644 --- a/src/content/ja/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx +++ b/src/content/ja/administrator-manual/databases/dac-general-configurations/unmasking-zones.mdx @@ -20,12 +20,12 @@ Unmasking Zonesを設定するには、まず[Allowed Zones設定](../../general 2. Unmasking Zonesのラジオボタンを`On`に変更し`+ Add Configuration`ボタンを押します。
-![image-20250515-085639.png](/administrator-manual/databases/dac-general-configurations/unmasking-zones/image-20250515-085639.png) +image-20250515-085639.png
1. Unmasking Zonesに追加したいAllowed Zone名を選択します。
- ![Allowed Zone追加](/administrator-manual/databases/dac-general-configurations/unmasking-zones/image-20250411-080251.png) + Allowed Zone追加
Allowed Zone追加
@@ -43,7 +43,7 @@ Unmasking zones設定はAllowed Zonesの値を使用するため、IP（帯域 1. Unmasking zones一覧で削除したい特定Allowed zoneを選択し`Delete`ボタンを押します。
- ![image-20250411-080409.png](/administrator-manual/databases/dac-general-configurations/unmasking-zones/image-20250411-080409.png) + image-20250411-080409.png
2. `Save Changes`ボタンを押して変更事項を保存します。 diff --git a/src/content/ja/administrator-manual/databases/db-access-control.mdx b/src/content/ja/administrator-manual/databases/db-access-control.mdx index 4bdb0fec..72c5132b 100644 --- a/src/content/ja/administrator-manual/databases/db-access-control.mdx +++ b/src/content/ja/administrator-manual/databases/db-access-control.mdx @@ -11,7 +11,7 @@ DB Access Controlメニューでは、高いレベルでデータベースアク 最初のQueryPieユーザー認証からデータベースアクセスまでIP帯域別統制、長期未接続統制、時間および曜日別統制、テーブル/カラム照会制限などで重要データを安全に保護でき、セキュリティポリシーに対するすべての変更事項はユーザーセッションに即座に適用されてアップデートされた措置をリアルタイムで適用できます。
-![Administrator > Databases > DB Access Control > Access Control](/administrator-manual/databases/db-access-control/screenshot-20240731-113229.png) +Administrator > Databases > DB Access Control > Access Control
Administrator > Databases > DB Access Control > Access Control
diff --git a/src/content/ja/administrator-manual/databases/db-access-control/access-control.mdx b/src/content/ja/administrator-manual/databases/db-access-control/access-control.mdx index 2afeee78..16a6464c 100644 --- a/src/content/ja/administrator-manual/databases/db-access-control/access-control.mdx +++ b/src/content/ja/administrator-manual/databases/db-access-control/access-control.mdx @@ -22,7 +22,7 @@ Access Controlページでは、QueryPieに登録されたユーザーおよび * Locked Accounts：アカウントロック条件によりロックされたユーザーを確認でき、ロックを解除できます。
-![Administrator > Databases > DB Access Control > Access Control](/administrator-manual/databases/db-access-control/access-control/image-20251209-061107.png) +Administrator > Databases > DB Access Control > Access Control
Administrator > Databases > DB Access Control > Access Control
@@ -34,7 +34,7 @@ Administrator > Databases > DB Access Control > Access Control Access Controlページ内Groups / Usersタブのリストで特定ユーザーまたはグループ行をクリックすると詳細画面でprivilegeを付与された対象情報を確認できます。
-![特定ユーザーのアクセス制御詳細ページ](/administrator-manual/databases/db-access-control/access-control/image-20251218-085542.png) +特定ユーザーのアクセス制御詳細ページ
特定ユーザーのアクセス制御詳細ページ
@@ -73,16 +73,16 @@ Access Controlページ内Groups / Usersタブのリストで特定ユーザー 3. `Grant Privilege`ボタンをクリックします。 4. ポップアップウィンドウでAccess Control LevelでHostを選択します。（基本値：Host）
- ![image-20251218-095117.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-095117.png) + image-20251218-095117.png
5. privilegeを付与するコネクションを選択し、特定privilege typeを選択します。
- ![image-20251218-095406.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-095406.png) + image-20251218-095406.png
6. 必要な場合、Expiration dateでprivilege期限切れ日を設定した後`Grant`ボタンを押します。 7. 権限を付与するコネクション複数個を選択して一括的に権限を付与することもできます。
- ![image-20251218-095817.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-095817.png) + image-20251218-095817.png
@@ -100,20 +100,20 @@ Access Controlページ内Groups / Usersタブのリストで特定ユーザー 3. `Grant Privilege`ボタンをクリックします。 4. ポップアップウィンドウでAccess Control LevelでSchema（Logical DB）を選択します。（基本値：Host）
- ![image-20251218-104148.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-104148.png) + image-20251218-104148.png
5. Connections項目で対象コネクションを選択します。スキーマレベルは一度に複数のコネクションに多重設定が不可能です。コネクションを選択すると右側のprivilege項目に基本的にselect権限が必要なスキーマに自動的にSELECT privilegeが付与されたことが見えます。管理者はこの項目を削除することもできますが、その場合Web editorまたはproxyでスキーマ構造を照会する時点にエラーが発生する可能性があるため、可能な限りこの項目を削除しないことをお勧めします。 6. privilegeを割り当てる特定スキーマ（論理DB）を指定するために`Add Item`ボタンを押します。
下に対象を追加できる行が追加されます。schema構造があるDBMS（Oracle、Postgresなど）は対象名を入力する時、必ず`{database名}`.`{schema名}`の形式で入力する必要があります。MySQLのようにschema構造がないDBMSは論理DB名のみ入力すれば 됩니다。
- Oracle例：ORCLDB.TESTUSER
- PostgreSQL例：testdb.test_schema
- MySQL例：sakila
- ![image-20251218-105030.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-105030.png) + image-20251218-105030.png
7. privilege割り当てはまずポップアップウィンドウ右側上部のHost Level Privilege項目で希望するprivilege typeを選択します。（スキーマレベルprivilegeはhost level privilegeの範囲内でのみ付与が可能なためです。例えばRead/WriteをHost Level Privilegeで選択した場合、その範囲内でSELECT、INSERTなどを付与できますが、Read-OnlyをHost Level Privilegeで選択した場合、SELECTのみ指定できます。）
- ![image-20251218-110506.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-110506.png) + image-20251218-110506.png
8. 下に表示されるHost Level Others、Host Level Functionsは設定を見るだけです。修正するためにはDatabases > DB Access Control > Privilege Typeメニューで該当Privilege Typeを修正する必要があります。Host LevelのPrivilegeの属性によりSchema Levelもprivilegeが従属するため、上位の情報を確認する用途で使用されます。
- ![image-20251218-111204.png](/administrator-manual/databases/db-access-control/access-control/image-20251218-111204.png) + image-20251218-111204.png
9. 必要な場合、Expiration dateでprivilege期限切れ日を設定した後`Grant`ボタンを押します。 @@ -134,7 +134,7 @@ Access Controlページ内Groups / Usersタブのリストで特定ユーザー ### Access Control権限回収
-![Administrator > Databases > DB Access Control > Access Control > Details](/administrator-manual/databases/db-access-control/access-control/image-20241209-122146.png) +Administrator > Databases > DB Access Control > Access Control > Details
Administrator > Databases > DB Access Control > Access Control > Details
@@ -168,7 +168,7 @@ Administrator > Databases > DB Access Control > Access Control > Det ### コネクションロックアカウント解除（Locked Account）
-![Administrator > Databases > DB Access Control > Access Control > Locked Account](/administrator-manual/databases/db-access-control/access-control/image-20241209-123011.png) +Administrator > Databases > DB Access Control > Access Control > Locked Account
Administrator > Databases > DB Access Control > Access Control > Locked Account
@@ -179,7 +179,7 @@ Administrator > Databases > DB Access Control > Access Control > Loc 3. ロック解除しようとする項目を選択後右側`Unlock`をクリックしてコネクションロックを解除します。
-![image-20241209-123358.png](/administrator-manual/databases/db-access-control/access-control/image-20241209-123358.png) +image-20241209-123358.png
1. コネクションロックおよびロック解除履歴はAudit > Databases > Account Lock Historyメニューで確認できます。 @@ -189,7 +189,7 @@ Administrator > Databases > DB Access Control > Access Control > Loc **テーブルタグでアクセス制御**

Databases > General > ConfigurationsでNew DAC Policy Managementを有効化した場合、
-![image-20250703-050924.png](/administrator-manual/databases/db-access-control/access-control/image-20250703-050924.png) +image-20250703-050924.png
Access Controlで特定ユーザーにアクセス許可されたコネクションに対して特定タグが付与されたテーブルのみアクセス可能になるよう制御できます。 @@ -205,7 +205,7 @@ Access Controlで特定ユーザーにアクセス許可されたコネクショ 2. 詳細画面でAccess TypeをTag-based table accessで選択してタグを追加します。既存のタグ（テーブルに付与されたタグ）のみ選択して使用できます。
-![image-20250703-051824.png](/administrator-manual/databases/db-access-control/access-control/image-20250703-051824.png) +image-20250703-051824.png
もしTag-based table access機能を有効化した状態でどのタグも登録しないと該当コネクションのすべてのテーブルにアクセスできなくなります。
diff --git a/src/content/ja/administrator-manual/databases/db-access-control/privilege-type.mdx b/src/content/ja/administrator-manual/databases/db-access-control/privilege-type.mdx index 3764562b..b52945e9 100644 --- a/src/content/ja/administrator-manual/databases/db-access-control/privilege-type.mdx +++ b/src/content/ja/administrator-manual/databases/db-access-control/privilege-type.mdx @@ -20,7 +20,7 @@ SQL構文はANSI SQL基準で分類されており、Redisの場合は別途のP
-![Administrator > Databases > DB Access Control > Privilege Type](/administrator-manual/databases/db-access-control/privilege-type/image-20240725-071543.png) +Administrator > Databases > DB Access Control > Privilege Type
Administrator > Databases > DB Access Control > Privilege Type
diff --git a/src/content/ja/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx b/src/content/ja/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx index bf11aad8..2fa0f21c 100644 --- a/src/content/ja/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx +++ b/src/content/ja/administrator-manual/databases/ledger-management/ledger-approval-rules.mdx @@ -21,7 +21,7 @@ import { Callout } from 'nextra/components' 元帳テーブルポリシー適用時強制化する承認規則を別途作成し、管理できます。
-![Administrator > Databases > Ledger Management > Ledger Approval Rules](/administrator-manual/databases/ledger-management/ledger-approval-rules/Screenshot-2024-12-18-at-11.52.33-AM.png) +Administrator > Databases > Ledger Management > Ledger Approval Rules
Administrator > Databases > Ledger Management > Ledger Approval Rules
diff --git a/src/content/ja/administrator-manual/databases/ledger-management/ledger-table-policy.mdx b/src/content/ja/administrator-manual/databases/ledger-management/ledger-table-policy.mdx index 96f2a906..f9330d98 100644 --- a/src/content/ja/administrator-manual/databases/ledger-management/ledger-table-policy.mdx +++ b/src/content/ja/administrator-manual/databases/ledger-management/ledger-table-policy.mdx @@ -25,7 +25,7 @@ DBコネクション単位でPolicyを作成し、コネクション内の元帳 設定後、ユーザーが該当テーブルでUPDATEなど修正クエリおよびデータエクスポートを試行する場合、該当承認規則を通じたSQL Requestを設定できます。
-![Administrator > Databases > Ledger Management > Ledger Table Policy](/administrator-manual/databases/ledger-management/ledger-table-policy/Screenshot-2024-12-18-at-11.46.38-AM.png) +Administrator > Databases > Ledger Management > Ledger Table Policy
Administrator > Databases > Ledger Management > Ledger Table Policy
@@ -41,7 +41,7 @@ Administrator > Databases > Ledger Management > Ledger Table Policy 一つのDBコネクション単位でLedger Table Policy一覧にポリシーが作成されたことを確認できます。
-![Administrator > Databases > Ledger Management > Ledger Table Policy > Details](/administrator-manual/databases/ledger-management/ledger-table-policy/Screenshot-2024-12-18-at-11.47.34-AM.png) +Administrator > Databases > Ledger Management > Ledger Table Policy > Details
Administrator > Databases > Ledger Management > Ledger Table Policy > Details
diff --git a/src/content/ja/administrator-manual/databases/monitoring.mdx b/src/content/ja/administrator-manual/databases/monitoring.mdx index 752c1519..1055c107 100644 --- a/src/content/ja/administrator-manual/databases/monitoring.mdx +++ b/src/content/ja/administrator-manual/databases/monitoring.mdx @@ -24,14 +24,14 @@ Proxy Managementはセッション強制機能が以前から存在していて
-![Databases > Monitoring > Running Queries](/administrator-manual/databases/monitoring/image-20250512-101633.png) +Databases > Monitoring > Running Queries
Databases > Monitoring > Running Queries
-![Databases > Monitoring > Proxy Management](/administrator-manual/databases/monitoring/image-20250512-104613.png) +Databases > Monitoring > Proxy Management
Databases > Monitoring > Proxy Management
diff --git a/src/content/ja/administrator-manual/databases/monitoring/proxy-management.mdx b/src/content/ja/administrator-manual/databases/monitoring/proxy-management.mdx index c4cb8128..9d6c36a5 100644 --- a/src/content/ja/administrator-manual/databases/monitoring/proxy-management.mdx +++ b/src/content/ja/administrator-manual/databases/monitoring/proxy-management.mdx @@ -20,7 +20,7 @@ DataGripやDBeaverのような3rd party toolを通じてクエリを実行する * **Status** : 有効有無を表示します。
-![Administrator > Databases > Monitoring > Proxy Management](/administrator-manual/databases/monitoring/proxy-management/image-20250512-113752.png) +Administrator > Databases > Monitoring > Proxy Management
Administrator > Databases > Monitoring > Proxy Management
@@ -38,7 +38,7 @@ Administrator > Databases > Monitoring > Proxy Management アクセスを許可するコネクションでProxy使用有無を有効化します。
-![image-20240725-070857.png](/administrator-manual/databases/monitoring/proxy-management/image-20240725-070857.png) +image-20240725-070857.png
1. Database設定メニューからDB Connectionsメニューに移動します。 diff --git a/src/content/ja/administrator-manual/databases/monitoring/running-queries.mdx b/src/content/ja/administrator-manual/databases/monitoring/running-queries.mdx index 48f44e37..cf52bdfb 100644 --- a/src/content/ja/administrator-manual/databases/monitoring/running-queries.mdx +++ b/src/content/ja/administrator-manual/databases/monitoring/running-queries.mdx @@ -14,7 +14,7 @@ Running QueriesはWeb editorやWorkflowおよびProxyを通じて実行したク ### Running Queries照会
-![Databases > Monitoring > Running Queries](/administrator-manual/databases/monitoring/running-queries/image-20250512-110402.png) +Databases > Monitoring > Running Queries
Databases > Monitoring > Running Queries
@@ -24,7 +24,7 @@ Databases > Monitoring > Running Queries 2. 当日基準で降順でログが照会されます。 3. テーブル左上のフィルターボタンをクリックしてAND/OR条件で以下のフィルタリングが可能です。
- ![image-20240730-081641.png](/administrator-manual/databases/monitoring/running-queries/image-20240730-081641.png) + image-20240730-081641.png
1. **SQL Type** : SQL構文タイプ 2. **Action At** : クエリ実行日時範囲 @@ -61,7 +61,7 @@ Databases > Monitoring > Running Queries 各行をクリックすると詳細情報照会が可能です。
-![Databases > Monitoring > Running Queries > Running Query Details](/administrator-manual/databases/monitoring/running-queries/image-20250512-110509.png) +Databases > Monitoring > Running Queries > Running Query Details
Databases > Monitoring > Running Queries > Running Query Details
@@ -95,7 +95,7 @@ Proxyを通じて実行したクエリ情報は照会できますが停止でき
-![クエリ停止](/administrator-manual/databases/monitoring/running-queries/image-20250512-111342.png) +クエリ停止
クエリ停止
diff --git a/src/content/ja/administrator-manual/databases/new-policy-management.mdx b/src/content/ja/administrator-manual/databases/new-policy-management.mdx index 5940aa07..cb93d922 100644 --- a/src/content/ja/administrator-manual/databases/new-policy-management.mdx +++ b/src/content/ja/administrator-manual/databases/new-policy-management.mdx @@ -25,7 +25,7 @@ General > Company management > Securityの下位項目中DB Connection Sec （基本値Disable）
-![Enable New DAC Policy Management](/administrator-manual/databases/new-policy-management/image-20250307-114537.png) +Enable New DAC Policy Management
Enable New DAC Policy Management
diff --git a/src/content/ja/administrator-manual/databases/new-policy-management/data-paths.mdx b/src/content/ja/administrator-manual/databases/new-policy-management/data-paths.mdx index 462a6ee1..8ac1c184 100644 --- a/src/content/ja/administrator-manual/databases/new-policy-management/data-paths.mdx +++ b/src/content/ja/administrator-manual/databases/new-policy-management/data-paths.mdx @@ -25,7 +25,7 @@ Data Pathsメニューではテーブルとカラムにタグを割り当て、 テーブルタギングはData Pathsメニューで管理でき、タグを通じてテーブルを体系的に分類し、管理できます。
-![image-20250307-121743.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-121743.png) +image-20250307-121743.png
1. 左側サイドバーで **Policy Management** セクション下の **Data Paths** をクリックします。 @@ -38,7 +38,7 @@ Data Pathsメニューではテーブルとカラムにタグを割り当て、 5. すべての情報を入力した後 **OK** ボタンをクリックしてテーブルを追加します。
-![image-20250307-122237.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-122237.png) +image-20250307-122237.png
1. テーブルが追加されると一覧に表示され、詳細ページで**「Add Tags」** ボタンをクリックして新しいタグを追加できます。 @@ -59,7 +59,7 @@ Data Pathsメニューではテーブルとカラムにタグを割り当て、 タグを通じてカラムを体系的に分類でき、マスキングなどのポリシーを効果的に一括適用できます。
-![image-20250307-124339.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-124339.png) +image-20250307-124339.png
1. **Data Paths** メニューの上部タブで **Columns** タブを選択します。 @@ -72,7 +72,7 @@ Data Pathsメニューではテーブルとカラムにタグを割り当て、 4. すべての情報を入力した後 **OK** ボタンをクリックしてカラムを追加します。
-![image-20250307-124802.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-124802.png) +image-20250307-124802.png
1. カラムが追加されると一覧に表示され、詳細ページで**「Add Tags」** ボタンをクリックして新しいタグを追加できます。 @@ -108,7 +108,7 @@ Data Pathsメニューで設定したタグを基にテーブルアクセス権 2. 付与された権限内でタグベースアクセス制御設定（Access Type）
-![image-20250307-125727.png](/administrator-manual/databases/new-policy-management/data-paths/image-20250307-125727.png) +image-20250307-125727.png
1. **Access Control** メニューでアクセス権限を設定するユーザーを選択し **Grant Permission** で権限を付与します。 diff --git a/src/content/ja/administrator-manual/databases/new-policy-management/data-policies.mdx b/src/content/ja/administrator-manual/databases/new-policy-management/data-policies.mdx index a7fd5b4a..ad21d389 100644 --- a/src/content/ja/administrator-manual/databases/new-policy-management/data-policies.mdx +++ b/src/content/ja/administrator-manual/databases/new-policy-management/data-policies.mdx @@ -15,7 +15,7 @@ Data PoliciesはQueryPieでデータアクセス制御、データマスキン ### ポリシー作成画面アクセス
-![image-20250307-131024.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131024.png) +image-20250307-131024.png
1. 左側サイドバーで **Policy Management** セクションを展開します。 @@ -26,7 +26,7 @@ Data PoliciesはQueryPieでデータアクセス制御、データマスキン ### ポリシー基本情報設定
-![image-20250307-131052.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131052.png) +image-20250307-131052.png
ポリシー作成画面の **Information** セクションで以下の情報を設定します: @@ -45,27 +45,27 @@ QueryPieは以下のようなポリシータイプを提供します: * 正規表現ベースのマスキングパターンを使用して特定データパターンを検出し、マスキングします。（Masking Patterns） * ユーザーが該当カラムを照会する時`{masked}`形態で表示され、セルをクリックするとマスキング処理されたデータが表示されます。

- ![Screenshot-2025-03-07-at-10.23.47-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-10.23.47-PM.png) + Screenshot-2025-03-07-at-10.23.47-PM.png
2. **Table Access Restriction** * テーブルを対象にアクセス遮断ポリシーを適用します。 * ユーザーが該当テーブルを照会しようとする時アクセスが遮断され、権限なしメッセージが表示されます。 * メッセージ: `"You don't have permission to access the table 'database.table'. Please check your privileges."`

- ![Screenshot-2025-03-07-at-10.36.58-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-10.36.58-PM.png) + Screenshot-2025-03-07-at-10.36.58-PM.png
3. **Column Access Restriction** * カラムを対象にアクセス遮断ポリシーを適用します。 * ユーザーが該当カラムを照会しようとする時`{restricted}`形態で表示され、アクセスが遮断されます。

- ![Screenshot-2025-03-07-at-10.34.20-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-10.34.20-PM.png) + Screenshot-2025-03-07-at-10.34.20-PM.png
4. **Table Access Justification Requirement** * 特定テーブルに対する作業時理由入力を強制化します。 * ユーザーが選択された作業（例：SELECTクエリ、データエクスポート）を実行する時理由入力モーダルが表示されます。 * 入力された理由はQuery AuditのExecution Reasonに記録されます。
- ![Screenshot-2025-03-07-at-11.01.28-PM.png](/administrator-manual/databases/new-policy-management/data-policies/Screenshot-2025-03-07-at-11.01.28-PM.png) + Screenshot-2025-03-07-at-11.01.28-PM.png
5. **Sensitive Data Access Monitoring** * 管理者が特定テーブルまたはカラムを機密情報として指定し、アクセスする場合Alertを発生させます。 @@ -74,14 +74,14 @@ QueryPieは以下のようなポリシータイプを提供します: * 特定テーブルに対して`INSERT`, `UPDATE`, `DELETE`クエリを実行する場合Workflowで承認手順を経るよう強制します。 * このポリシーを作成する前にGeneral > Workflow Management > Approval RulesでSQL Request TypeのApproval Ruleをまず作成しておく必要があります。`INSERT`, `UPDATE`, `DELETE`を実行するのは実行する人に該当privilegeが付与されていることを前提とします。クエリを実行する人がリクエスト者本人になるようにするには、以下の図のようにExecution項目のAssignee for Executionに「Allow Assginee selection (All Users)が選択されている必要があり、`INSERT`, `UPDATE`, `DELETE`権限はあるが管理者でない人が承認を経てクエリを実行できます。
- ![General > Workflow Management > Approval RulesにSQL Request形式のApproval ruleを作成](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-153240.png) + General > Workflow Management > Approval RulesにSQL Request形式のApproval ruleを作成
General > Workflow Management > Approval RulesにSQL Request形式のApproval ruleを作成
* Approval Ruleが作成されていれば以下の図のようにポリシーと連携するApproval Ruleを指定できます。
- ![Databases>Policy Management>Data PoliciesでSQL Request形式の事前に作成したApproval Ruleを指定](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-154218.png) + Databases>Policy Management>Data PoliciesでSQL Request形式の事前に作成したApproval Ruleを指定
Databases>Policy Management>Data PoliciesでSQL Request形式の事前に作成したApproval Ruleを指定
@@ -93,7 +93,7 @@ QueryPieは以下のようなポリシータイプを提供します: ポリシー作成画面の **User Scope** セクションでポリシーが適用されるユーザー範囲を設定します。
-![image-20250307-131315.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131315.png) +image-20250307-131315.png
#### Scope Type @@ -119,7 +119,7 @@ User scopeのscope typeが **Everyone** の場合のみExclusion対象を指定 ポリシー作成画面の **Data Scope** セクションでポリシーが適用されるデータを設定します。
-![image-20250307-131634.png](/administrator-manual/databases/new-policy-management/data-policies/image-20250307-131634.png) +image-20250307-131634.png
#### Scope Type @@ -134,13 +134,13 @@ User scopeのscope typeが **Everyone** の場合のみExclusion対象を指定 2. **Specific data path** : 特定データ経路を直接指定するオプションです。 **[11.0.0]** * このオプションを選択した後Add tartgetボタンを押して出力されるポップアップダイアログでDatabase、Schema、Table、Columnを指定でき、正規表現も使用できます。

- ![直接経路指定](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-162342.png) + 直接経路指定
直接経路指定
- ![正規表現を使用して対象指定](/administrator-manual/databases/new-policy-management/data-policies/image-20250629-162448.png) + 正規表現を使用して対象指定
正規表現を使用して対象指定
diff --git a/src/content/ja/administrator-manual/databases/new-policy-management/exception-management.mdx b/src/content/ja/administrator-manual/databases/new-policy-management/exception-management.mdx index 25569d04..974d0e3a 100644 --- a/src/content/ja/administrator-manual/databases/new-policy-management/exception-management.mdx +++ b/src/content/ja/administrator-manual/databases/new-policy-management/exception-management.mdx @@ -14,7 +14,7 @@ import { Callout } from 'nextra/components' ### Workflowを通じたポリシー例外管理
-![image-20250629-172021.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250629-172021.png) +image-20250629-172021.png
Databases > Data Policies > Exception ManagementにWorkflowタブにWokflowで提出され承認された一時ポリシー例外件が表示され、有効状態を管理できます。 @@ -34,7 +34,7 @@ Databases > Data Policies > Exception ManagementにWorkflowタブにWokflo ### 管理者が直接ポリシー例外設定
-![Databases > Policy Management > Exception Management のManualタブ](/administrator-manual/databases/new-policy-management/exception-management/image-20250727-211515.png) +Databases > Policy Management > Exception Management のManualタブ
Databases > Policy Management > Exception Management のManualタブ
@@ -53,7 +53,7 @@ Workflowのポリシー例外申請および管理者の手動ポリシー例外
-![手動ポリシー例外作成](/administrator-manual/databases/new-policy-management/exception-management/image-20250727-210957.png) +手動ポリシー例外作成
手動ポリシー例外作成
@@ -85,7 +85,7 @@ Workflowのポリシー例外申請および管理者の手動ポリシー例外 一覧のStatus列でActive、Inactive中一つを選択して即座に状態変更ができ、ポリシー例外を削除したり新しく作ったりせずに簡単に対応できます。
-![image-20250716-055008.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250716-055008.png) +image-20250716-055008.png
#### 手動で作成したポリシー例外修正 @@ -94,14 +94,14 @@ Workflowのポリシー例外申請および管理者の手動ポリシー例外 （Exception Typeは変更できません。）
-![image-20250716-055149.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250716-055149.png) +image-20250716-055149.png
#### 手動で作成したポリシー例外削除
-![image-20250716-055525.png](/administrator-manual/databases/new-policy-management/exception-management/image-20250716-055525.png) +image-20250716-055525.png
diff --git a/src/content/ja/administrator-manual/databases/policies/data-access.mdx b/src/content/ja/administrator-manual/databases/policies/data-access.mdx index 567440b7..736b7cde 100644 --- a/src/content/ja/administrator-manual/databases/policies/data-access.mdx +++ b/src/content/ja/administrator-manual/databases/policies/data-access.mdx @@ -16,7 +16,7 @@ Data Accessメニューでポリシーを設定するコネクションを選択 新しいテーブル/カラムアクセス制限ポリシーをコネクション基準で登録します。
-![Administrator > Databases > Policies > Data Access ](/administrator-manual/databases/policies/data-access/image-20240725-072304.png) +Administrator > Databases > Policies > Data Access
Administrator > Databases > Policies > Data Access
@@ -35,7 +35,7 @@ Administrator > Databases > Policies > Data Access ### テーブル/カラムアクセス制限ポリシーに規則登録
-![Administrator > Databases > Policies > Data Access > Details > Add Rule](/administrator-manual/databases/policies/data-access/data-access-02.png) +Administrator > Databases > Policies > Data Access > Details > Add Rule
Administrator > Databases > Policies > Data Access > Details > Add Rule
@@ -57,7 +57,7 @@ Rule Listタブで規則が登録されたことを確認できます。 これでユーザーが該当データを照会すると、テーブルにポリシーが適用された場合テーブル自体を照会できず、カラムに規則が適用された場合 *`{RESTRICTED}`* で表示されます。
-![SQL Editor > ポリシーが適用されたデータ照会時 *`{RESTRICTED}`* で表示](/administrator-manual/databases/policies/data-access/data-access-03.png) +SQL Editor > ポリシーが適用されたデータ照会時 *`{RESTRICTED}`* で表示
SQL Editor > ポリシーが適用されたデータ照会時 *`{RESTRICTED}`* で表示
@@ -77,7 +77,7 @@ Administrator > Databases > Connection Management > DB Connectionsメ
-![Logsタブでログ確認](/administrator-manual/databases/policies/data-access/image-20250512-040339.png) +Logsタブでログ確認
Logsタブでログ確認
@@ -95,7 +95,7 @@ Logsタブでログ確認 7. **Action At** ：クエリを実行した時点です。 4. Logタブの行をクリックすると詳細画面で実行されたクエリを確認できます。
- ![ログの詳細画面でクエリ内容確認](/administrator-manual/databases/policies/data-access/image-20250512-040436.png) + ログの詳細画面でクエリ内容確認
ログの詳細画面でクエリ内容確認
diff --git a/src/content/ja/administrator-manual/databases/policies/data-masking.mdx b/src/content/ja/administrator-manual/databases/policies/data-masking.mdx index aa1091d3..3cf1f3c8 100644 --- a/src/content/ja/administrator-manual/databases/policies/data-masking.mdx +++ b/src/content/ja/administrator-manual/databases/policies/data-masking.mdx @@ -17,7 +17,7 @@ Data Maskingメニューでポリシーを設定するコネクションを選 新しいマスキングポリシーをコネクション基準で登録します。
-![Administrator > Databases > Policies > Data Masking](/administrator-manual/databases/policies/data-masking/image-20240725-072925.png) +Administrator > Databases > Policies > Data Masking
Administrator > Databases > Policies > Data Masking
@@ -36,7 +36,7 @@ Administrator > Databases > Policies > Data Masking ### データマスキングポリシーに規則登録
-![Administrator > Databases > Policies > Data Masking > Rule Details](/administrator-manual/databases/policies/data-masking/image-20240725-073032.png) +Administrator > Databases > Policies > Data Masking > Rule Details
Administrator > Databases > Policies > Data Masking > Rule Details
@@ -76,7 +76,7 @@ Database Settings > Connection Management > DB Connectionsメニューで
-![image-20250512-041023.png](/administrator-manual/databases/policies/data-masking/image-20250512-041023.png) +image-20250512-041023.png
1. ポリシーリストで生成したポリシーの個別項目（行）をクリックして詳細ページに移動します。 diff --git a/src/content/ja/administrator-manual/databases/policies/masking-pattern.mdx b/src/content/ja/administrator-manual/databases/policies/masking-pattern.mdx index 8c661748..da89cec5 100644 --- a/src/content/ja/administrator-manual/databases/policies/masking-pattern.mdx +++ b/src/content/ja/administrator-manual/databases/policies/masking-pattern.mdx @@ -22,7 +22,7 @@ Masing Patternページで登録されたマスキングパターンを照会で （パターン名で検索可能）
-![Administrator > Databases > General > Masking Pattern](/administrator-manual/databases/policies/masking-pattern/image-20250826-005621.png) +Administrator > Databases > General > Masking Pattern
Administrator > Databases > General > Masking Pattern
@@ -34,7 +34,7 @@ Administrator > Databases > General > Masking Pattern テーブルで詳細情報を照会したいアイテムをクリックするとDrawerが開き、詳細情報を照会、変更、または削除できます。
-![Administrator > Databases > General > Masking Pattern > Details](/administrator-manual/databases/policies/masking-pattern/image-20250826-005930.png) +Administrator > Databases > General > Masking Pattern > Details
Administrator > Databases > General > Masking Pattern > Details
@@ -60,7 +60,7 @@ Administrator > Databases > General > Masking Pattern > Details 必要な情報をすべて入力後`Save`ボタンを押して保存します。
-![Create Pattern](/administrator-manual/databases/policies/masking-pattern/screenshot-20240731-174002.png) +Create Pattern
Create Pattern
diff --git a/src/content/ja/administrator-manual/databases/policies/policy-exception.mdx b/src/content/ja/administrator-manual/databases/policies/policy-exception.mdx index bd06ec31..2514bd05 100644 --- a/src/content/ja/administrator-manual/databases/policies/policy-exception.mdx +++ b/src/content/ja/administrator-manual/databases/policies/policy-exception.mdx @@ -10,7 +10,7 @@ Workflowを通じて申請されたUnmasking Requestが承認処理されると
-![Policy Exception](/administrator-manual/databases/policies/policy-exception/image-20241101-011820.png) +Policy Exception
Policy Exception
diff --git a/src/content/ja/administrator-manual/databases/policies/sensitive-data.mdx b/src/content/ja/administrator-manual/databases/policies/sensitive-data.mdx index 0515becd..feac07c8 100644 --- a/src/content/ja/administrator-manual/databases/policies/sensitive-data.mdx +++ b/src/content/ja/administrator-manual/databases/policies/sensitive-data.mdx @@ -18,7 +18,7 @@ Sensitive Dataメニューでポリシーを設定するコネクションを選 新しい機密データポリシーをコネクション基準で登録します。
-![Administrator > Databases > Policies > Sensitive Data](/administrator-manual/databases/policies/sensitive-data/image-20240729-054311.png) +Administrator > Databases > Policies > Sensitive Data
Administrator > Databases > Policies > Sensitive Data
@@ -39,7 +39,7 @@ Administrator > Databases > Policies > Sensitive Data ポリシーを生成した後、実際にポリシーを適用するデータの経路を規則として登録します。
-![Administrator > Databases > Policies > Sensitive Data > Rule List](/administrator-manual/databases/policies/sensitive-data/image-20240820-120656.png) +Administrator > Databases > Policies > Sensitive Data > Rule List
Administrator > Databases > Policies > Sensitive Data > Rule List
@@ -64,7 +64,7 @@ Rule Listタブで規則が登録されたことを確認できます。 10.2.8からLogタブで見ることができるSensitive dataアクセス履歴にユーザーが実行したクエリを含むよう改善されました。 Log行をクリックすると出力される詳細情報にユーザーが実行したクエリを見ることができます。
-![Sensitive Data Logのクエリ内容表示](/administrator-manual/databases/policies/sensitive-data/image-20250410-065516.png) +Sensitive Data Logのクエリ内容表示
Sensitive Data Logのクエリ内容表示
diff --git a/src/content/ja/administrator-manual/general.mdx b/src/content/ja/administrator-manual/general.mdx index aa74ffad..9d32b663 100644 --- a/src/content/ja/administrator-manual/general.mdx +++ b/src/content/ja/administrator-manual/general.mdx @@ -9,7 +9,7 @@ title: 'General' Generalは管理者ページに移る最初の関門であり、セキュリティ設定管理、ユーザーおよびグループ管理、ワークフロー決裁ライン管理、統合連携およびAPIトークン管理など様々なQueryPie全般の一般設定を管理するためのページです。
-![Administrator > General > Company Management > Security](/administrator-manual/general/image-20240724-054109.png) +Administrator > General > Company Management > Security
Administrator > General > Company Management > Security
diff --git a/src/content/ja/administrator-manual/general/company-management.mdx b/src/content/ja/administrator-manual/general/company-management.mdx index 6cf20f16..ff1350c1 100644 --- a/src/content/ja/administrator-manual/general/company-management.mdx +++ b/src/content/ja/administrator-manual/general/company-management.mdx @@ -9,7 +9,7 @@ title: 'Company Management' Company ManagementはQueryPie製品の基本セキュリティおよび通知設定などを管理するためのメニューです。
-![Administrator > General > Company Management > General](/administrator-manual/general/company-management/image-20240724-055809.png) +Administrator > General > Company Management > General
Administrator > General > Company Management > General
diff --git a/src/content/ja/administrator-manual/general/company-management/alerts.mdx b/src/content/ja/administrator-manual/general/company-management/alerts.mdx index 3f098ce2..bb73d1b8 100644 --- a/src/content/ja/administrator-manual/general/company-management/alerts.mdx +++ b/src/content/ja/administrator-manual/general/company-management/alerts.mdx @@ -13,7 +13,7 @@ Alertsページでは、リソースアクセスに関連する通知機能を 潜在的なセキュリティインシデントを迅速に識別し解決でき、事前定義された閾値を超えるクエリや漏洩など、機密情報を保護できます。
-![Administrator > General > Company Management > Alerts](/administrator-manual/general/company-management/alerts/screenshot-20240728-223320.png) +Administrator > General > Company Management > Alerts
Administrator > General > Company Management > Alerts
@@ -196,7 +196,7 @@ Kubernetes APIリクエスト通知 Alertsページ右上の`Create Alert`ボタンをクリックして新しい通知を作成します。`OK`ボタンをクリックして通知作成を完了します。
-![Administrator > General > Company Management > Alerts > Create Alert](/administrator-manual/general/company-management/alerts/screenshot-20240729-141728.png) +Administrator > General > Company Management > Alerts > Create Alert
Administrator > General > Company Management > Alerts > Create Alert
@@ -396,7 +396,7 @@ Sensitive Data Access通知タイプ使用には機密データポリシーに * Specific Time Internal (Minutes) : 5
-![image-20251010-093016.png](/administrator-manual/general/company-management/alerts/image-20251010-093016.png) +image-20251010-093016.png
@@ -470,7 +470,7 @@ Databases > General > ConfigurationsでNew DAC Policy Management機能が Data Access通知はColumn Data Masking、Table Access Restriction、Column Access Restriction、Sensitive Data Access Monitoringの4つの**policy type**を選択できます。
-![image-20250727-222007.png](/administrator-manual/general/company-management/alerts/image-20250727-222007.png) +image-20250727-222007.png
* **Column Data Masking** @@ -504,7 +504,7 @@ Alertsページで詳細内容を照会したい通知を選択します。 右上`Save Changes`ボタンをクリックすると修正内容が反映されます。
-![Administrator > General > Company Management > Alerts > List Details (Details)](/administrator-manual/general/company-management/alerts/screenshot-20240729-154217.png) +Administrator > General > Company Management > Alerts > List Details (Details)
Administrator > General > Company Management > Alerts > List Details (Details)
@@ -517,7 +517,7 @@ Alertsリストで送信履歴を照会したい通知を選択します。 その後詳細ページ内Logで履歴を照会できます。
-![Administrator > General > Company Management > Alerts > List Details (Logs)](/administrator-manual/general/company-management/alerts/screenshot-20240729-154223.png) +Administrator > General > Company Management > Alerts > List Details (Logs)
Administrator > General > Company Management > Alerts > List Details (Logs)
diff --git a/src/content/ja/administrator-manual/general/company-management/allowed-zones.mdx b/src/content/ja/administrator-manual/general/company-management/allowed-zones.mdx index 009b5682..e4f42269 100644 --- a/src/content/ja/administrator-manual/general/company-management/allowed-zones.mdx +++ b/src/content/ja/administrator-manual/general/company-management/allowed-zones.mdx @@ -25,7 +25,7 @@ Allowed Zone名で検索が可能です。
-![Administrator > General > Company Management > Allowed Zones](/administrator-manual/general/company-management/allowed-zones/image-20251009-030815.png) +Administrator > General > Company Management > Allowed Zones
Administrator > General > Company Management > Allowed Zones
@@ -36,7 +36,7 @@ Administrator > General > Company Management > Allowed Zones Allowed Zonesリストで詳細情報を照会したいアイテムをクリックするとDrawerが開きます。
-![Administrator > General > Company Management > Allowed Zones > Allowed Zones Detail](/administrator-manual/general/company-management/allowed-zones/image-20251009-031233.png) +Administrator > General > Company Management > Allowed Zones > Allowed Zones Detail
Administrator > General > Company Management > Allowed Zones > Allowed Zones Detail
@@ -61,7 +61,7 @@ Drawer内Mapped List by Allowed Zones領域でAllowed Zoneが割り当てられ Allowed Zoneリストページで`Create Allowed Zone`ボタンをクリックするとAllowed Zone入力項目が出力されます。
-![Create Allowed Zone生成時に出力される入力項目](/administrator-manual/general/company-management/allowed-zones/image-20251009-031536.png) +Create Allowed Zone生成時に出力される入力項目
Create Allowed Zone生成時に出力される入力項目
@@ -82,7 +82,7 @@ Allowed Zoneリストで削除したいAllowed Zoneをチェックボックス ボタンをクリックし確認モーダルで`Delete`ボタンをクリックして削除を完了します。
-![削除オプション有効化](/administrator-manual/general/company-management/allowed-zones/screenshot-20240730-220112.png) +削除オプション有効化
削除オプション有効化
diff --git a/src/content/ja/administrator-manual/general/company-management/channels.mdx b/src/content/ja/administrator-manual/general/company-management/channels.mdx index 002ec78a..ac6af9d2 100644 --- a/src/content/ja/administrator-manual/general/company-management/channels.mdx +++ b/src/content/ja/administrator-manual/general/company-management/channels.mdx @@ -17,7 +17,7 @@ Administrator > General > Company Management > Channelsページで現 チャンネル名で検索が可能で、Channel Typeでフィルタリングできます。
-![Administrator > General > Company Management > Channels](/administrator-manual/general/company-management/channels/screenshot-20240808-172741.png) +Administrator > General > Company Management > Channels
Administrator > General > Company Management > Channels
@@ -26,7 +26,7 @@ Administrator > General > Company Management > Channels リスト内項目をクリックすると詳細情報を照会および変更できます。
-![Administrator > General > Company Management > Channels > List Details](/administrator-manual/general/company-management/channels/screenshot-20241211-191603.png) +Administrator > General > Company Management > Channels > List Details
Administrator > General > Company Management > Channels > List Details
@@ -38,7 +38,7 @@ Administrator > General > Company Management > Channels > List Detai Channelsページ右上の`Create Channel`ボタンをクリックするとチャンネル作成モーダルが表示されます。
-![Administrator > General > Company Management > Channels > Create Channel](/administrator-manual/general/company-management/channels/screenshot-20241211-154231.png) +Administrator > General > Company Management > Channels > Create Channel
Administrator > General > Company Management > Channels > Create Channel
@@ -109,7 +109,7 @@ Channelsページ内チャンネルリストで削除したいチャンネルを ボタンをクリックすると削除確認モーダルが出力されます。`OK`ボタンをクリックすると削除が完了します。
-![Administrator > General > Company Management > Channels > Delete確認モーダル](/administrator-manual/general/company-management/channels/screenshot-20240728-222004.png) +Administrator > General > Company Management > Channels > Delete確認モーダル
Administrator > General > Company Management > Channels > Delete確認モーダル
@@ -120,7 +120,7 @@ Administrator > General > Company Management > Channels > Delete確 #### 1. App作成
-![Slack API > Apps > Create an App](/administrator-manual/general/company-management/channels/screenshot-20240305-161015.png) +Slack API > Apps > Create an App
Slack API > Apps > Create an App
@@ -134,7 +134,7 @@ Slack API > Apps > Create an App #### 2-1. Webhookタイプで連携
-![Slack API > Apps > Settings > Incoming Webhooks](/administrator-manual/general/company-management/channels/screenshot-20240804-190716.png) +Slack API > Apps > Settings > Incoming Webhooks
Slack API > Apps > Settings > Incoming Webhooks
@@ -145,7 +145,7 @@ Slack API > Apps > Settings > Incoming Webhooks 3. 下部の`Add New Webhook to Workspace`をクリックします。
-![Slack内Webhook追加画面](/administrator-manual/general/company-management/channels/image-20240305-110658.png) +Slack内Webhook追加画面
Slack内Webhook追加画面
@@ -159,7 +159,7 @@ Slack内Webhook追加画面 1. 生成したAppをクリックしてアプリのSettingsページに進入した後、`App Manifest`メニューに移動します。 2. scopes領域に`chat:write`, `users:read`, `users:read.email`を追加した後保存します。
- ![Slack API > Apps > Settings > App Manifest](/administrator-manual/general/company-management/channels/screenshot-20241211-171140.png) + Slack API > Apps > Settings > App Manifest
Slack API > Apps > Settings > App Manifest
@@ -170,14 +170,14 @@ Slack内Webhook追加画面 5. 該当Slackチャンネルに移動して生成したアプリを追加します。（既にアプリを追加した状態であればこの段階はスキップできます） 6. チャンネル名をクリックしてChannel Detailモーダルを開き、モーダル下部でChannel IDをコピーします。コピーしたChannel IDをQueryPieチャンネル作成モーダルに貼り付けます。
- ![Slack App > Channel Detail](/administrator-manual/general/company-management/channels/screenshot-20241211-190312.png) + Slack App > Channel Detail
Slack App > Channel Detail
7. OAuth & PermissionsページでBot User OAuth Tokenをコピーし、QueryPieチャンネル作成モーダルに貼り付けます。
- ![Slack内OAuth & Permissionsページ - トークンコピー](/administrator-manual/general/company-management/channels/screenshot-20240804-190835.png) + Slack内OAuth & Permissionsページ - トークンコピー
Slack内OAuth & Permissionsページ - トークンコピー
diff --git a/src/content/ja/administrator-manual/general/company-management/general.mdx b/src/content/ja/administrator-manual/general/company-management/general.mdx index ea4f26fb..f687aff4 100644 --- a/src/content/ja/administrator-manual/general/company-management/general.mdx +++ b/src/content/ja/administrator-manual/general/company-management/general.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' Generalページでは、QueryPie全体の基本設定を変更できます。
-![Administrator > General > Company Management > General](/administrator-manual/general/company-management/general/image-20250822-103044.png) +Administrator > General > Company Management > General
Administrator > General > Company Management > General
@@ -33,7 +33,7 @@ Administrator > General > Company Management > General System Propertiesページでは、QueryPieシステムコンポーネントの設定値を確認し、ファイルで保存できます。
-![Administrator > General > Company Management > General > System Properties](/administrator-manual/general/company-management/general/image-20240805-014838.png) +Administrator > General > Company Management > General > System Properties
Administrator > General > Company Management > General > System Properties
@@ -45,7 +45,7 @@ Administrator > General > Company Management > General > System Prop Workflow Configurationsでは、決裁上申および承認関連の設定を変更します。
-![Screenshot-2025-08-25-at-5.36.19-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-08-25-at-5.36.19-PM.png) +Screenshot-2025-08-25-at-5.36.19-PM.png
### 最大承認期間設定 @@ -101,27 +101,27 @@ Allow users to submit requests in Urgent modeトグルで有効化します。 * 重要： * 選択されたAttributeの値には承認者のQueryPie Login IDが入力されていなければなりません。
- ![Admin > General > Users > Detail page > Profileタブ
](/administrator-manual/general/company-management/general/Screenshot-2025-06-12-at-1.33.58-PM.png) + Admin > General > Users > Detail page > Profileタブ<br/>
Admin > General > Users > Detail page > Profileタブ
* Administrator > General > Workflow Management > Approval Rulesページで新しい承認規則を追加または既存規則を修正する際、'Assignee for Approval'項目に'Allow Assignee selection (Attribute-Based)'を選択した後、承認者とマッピングするためのAttribute（例：teamLeader）を指定します。
- ![image-20251110-030113.png](/administrator-manual/general/company-management/general/image-20251110-030113.png) + image-20251110-030113.png
* 自己承認無効化時連動：もしApproval Rules設定で'Self Approval（自己承認）'オプションが無効化された場合、Attribute基盤で決定された承認者が要求者本人の場合には該当要求者を承認者として自動指定できません。この場合、ワークフロー設定またはシステムポリシーに従って承認者指定が失敗するか他の経路で処理される可能性があるため注意が必要です。 * Attribute値不在時通知 * もし上申者User Profileに該当Attribute値が空の場合（すなわち、承認者のLogin IDが指定されていない場合）、ワークフロー上申時に以下のような内容の通知モーダルが表示され要求提出が中断されます。上申者は管理者に問い合わせてプロフィールのAttribute値を設定しなければなりません。 * エラーメッセージ例：
- ![image-20250508-022114.png](/administrator-manual/general/company-management/general/image-20250508-022114.png) + image-20250508-022114.png
* Attribute値はあるが該当ユーザーが無効化された場合 * もし上申者User Profileに該当Attribute値で指定された承認者が無効化された場合、ワークフロー上申時にApprover欄に指定された承認者が表記されず、以下のような内容の通知モーダルが表示され要求提出が中断されます。 * エラーメッセージ例：
- ![Screenshot-2025-06-16-at-10.30.14-AM.png](/administrator-manual/general/company-management/general/Screenshot-2025-06-16-at-10.30.14-AM.png) + Screenshot-2025-06-16-at-10.30.14-AM.png
### Attribute基盤ワークフローメニュー非表示機能 (Use User Attribute to Hide Workflow Menu) @@ -129,7 +129,7 @@ Allow users to submit requests in Urgent modeトグルで有効化します。 Use User Attribute to Hide Workflow Menuトグルを有効化します。
-![Screenshot-2025-06-26-at-6.35.32-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-06-26-at-6.35.32-PM.png) +Screenshot-2025-06-26-at-6.35.32-PM.png
特定ユーザー属性（User Attribute）を基準にユーザーダッシュボードでWorkflowメニューを表示しないように設定する機能です。 @@ -149,14 +149,14 @@ Use User Attribute to Hide Workflow Menuトグルを有効化します。 もし無効化する場合、ユーザーpreference画面でApprover settingメニューが表示されません。
-![Allow Delegated Approvalスイッチ](/administrator-manual/general/company-management/general/image-20250926-112444.png) +Allow Delegated Approvalスイッチ
Allow Delegated Approvalスイッチ
-![代理決裁機能を無効化した状態のpreference](/administrator-manual/general/company-management/general/image-20250926-112201.png) +代理決裁機能を無効化した状態のpreference
代理決裁機能を無効化した状態のpreference
@@ -167,7 +167,7 @@ Allow Delegated Approvalスイッチ トグルをオンにすると、Workflowで上申されたSQL要求実行時にスロットリングを適用します。
-![Screenshot-2025-05-09-at-3.18.32-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-05-09-at-3.18.32-PM.png) +Screenshot-2025-05-09-at-3.18.32-PM.png
@@ -183,7 +183,7 @@ Allow Delegated Approvalスイッチ Redirect to custom page for SQL Requestsトグルを有効化します。
-![Screenshot-2025-05-09-at-8.33.07-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-05-09-at-8.33.07-PM.png) +Screenshot-2025-05-09-at-8.33.07-PM.png
このオプションを通じて、User AgentでLedgerテーブル対象にINSERT、UPDATE、DELETEクエリ実行によりワークフロー承認要求が発生する場合、`Send Request`ボタンクリック時にユーザーを事前に定義されたカスタムURLページにリダイレクトするかを決定します。 @@ -201,7 +201,7 @@ Redirect to custom page for SQL Requestsトグルを有効化します。 Select Request Types Allowed for Usersトグルを有効化します。
-![Screenshot-2025-05-09-at-8.40.28-PM.png](/administrator-manual/general/company-management/general/Screenshot-2025-05-09-at-8.40.28-PM.png) +Screenshot-2025-05-09-at-8.40.28-PM.png
このオプションを通じて、管理者がユーザーがアクセスし要求できるワークフローの要求（Request）タイプを選択的に制御できるようにします。 @@ -227,7 +227,7 @@ Select Request Types Allowed for Usersトグルを有効化します。 Workflowを通じてDB Access Requestを上申する場合、要求する権限に従って決裁線（Approval Rule）を特定できるようにするには「Use DB Privilege Type Based Approval」トグルを有効化します。
-![Use DB Privilege Type Based Approval](/administrator-manual/general/company-management/general/image-20250822-111454.png) +Use DB Privilege Type Based Approval
Use DB Privilege Type Based Approval
@@ -236,7 +236,7 @@ Use DB Privilege Type Based Approval `+Routing Rule`ボタンを押すと、privilegeに対する条件を指定して決裁線に対するルーティングを指定できます。
-![image-20250822-112026.png](/administrator-manual/general/company-management/general/image-20250822-112026.png) +image-20250822-112026.png
* **Routing Rule Name** : 識別しやすいルーティング規則の名前を入力します。 @@ -262,7 +262,7 @@ Use DB Privilege Type Based Approval WorkflowのSQL Requestを通じて実行するクエリを上申する際に実行計画結果を添付する「Attach Explain Results」機能を有効または無効化できるオプションを提供します。
-![image-20250825-002423.png](/administrator-manual/general/company-management/general/image-20250825-002423.png) +image-20250825-002423.png
管理者がこのオプションを有効化しても、WorkflowのSQL Request様式で「Attach Explain Results」はOffになっているため、ユーザーが必要時に明示的に「Attatch Explain Results」トグルスイッチをOnに変更しなければ実行計画結果が添付されます。 diff --git a/src/content/ja/administrator-manual/general/company-management/licenses.mdx b/src/content/ja/administrator-manual/general/company-management/licenses.mdx index fdecee6c..f73c5296 100644 --- a/src/content/ja/administrator-manual/general/company-management/licenses.mdx +++ b/src/content/ja/administrator-manual/general/company-management/licenses.mdx @@ -19,7 +19,7 @@ Licensesページは現在QueryPieで有効化された製品ライセンスキ
-![Administrator > General > Company Management > Licenses](/administrator-manual/general/company-management/licenses/image-20250926-124941.png) +Administrator > General > Company Management > Licenses
Administrator > General > Company Management > Licenses
diff --git a/src/content/ja/administrator-manual/general/company-management/security.mdx b/src/content/ja/administrator-manual/general/company-management/security.mdx index b5d305a9..df82513c 100644 --- a/src/content/ja/administrator-manual/general/company-management/security.mdx +++ b/src/content/ja/administrator-manual/general/company-management/security.mdx @@ -25,7 +25,7 @@ QueryPie Webログイン関連のセキュリティ設定を管理します。 QueryPieアカウントのロックおよび期限切れなどのセキュリティポリシーを設定できます。
-![Screenshot-2025-08-27-at-4.25.50-PM.png](/administrator-manual/general/company-management/security/Screenshot-2025-08-27-at-4.25.50-PM.png) +Screenshot-2025-08-27-at-4.25.50-PM.png
* **Account Expiration Period (Days)** : アカウント期限切れ処理のための長期未接続日数基準 @@ -48,7 +48,7 @@ QueryPieアカウントのロックおよび期限切れなどのセキュリテ QueryPieアカウントのパスワードポリシーを設定できます。
-![image-20250515-091250.png](/administrator-manual/general/company-management/security/image-20250515-091250.png) +image-20250515-091250.png
* **Maximum Password Age** : パスワード変更周期 (Default : 90日) @@ -71,7 +71,7 @@ QueryPieアカウントのパスワードポリシーを設定できます。 ウェブコンソールとエージェントのタイムアウトポリシーを設定できます。
-![image-20251009-051727.png](/administrator-manual/general/company-management/security/image-20251009-051727.png) +image-20251009-051727.png
* **Web Inactivity Timeout** : ウェブコンソールタイムアウト基準 (Default : 60分) @@ -95,7 +95,7 @@ QueryPieアカウントのパスワードポリシーを設定できます。 QueryPie接続時IP制限ポリシーを設定できます。
-![Screenshot-2025-06-26-at-2.14.46-PM.png](/administrator-manual/general/company-management/security/Screenshot-2025-06-26-at-2.14.46-PM.png) +Screenshot-2025-06-26-at-2.14.46-PM.png
* **All Users** : すべてのユーザーに適用されるIP制限設定 (Default : 0.0.0.0/0) @@ -115,7 +115,7 @@ QueryPie接続時IP制限ポリシーを設定できます。 * **Admin Page Access Control** : 管理者ページにアクセスできる管理者のIPを制限するポリシーを設定します。トグルを活性化して特定IPアドレスまたは帯域から接続する管理者のみ管理者ページにアクセスするよう制限できます。
- ![AdminページIPアクセス遮断時画面](/administrator-manual/general/company-management/security/image-20251212-161723.png) + AdminページIPアクセス遮断時画面
AdminページIPアクセス遮断時画面
@@ -134,14 +134,14 @@ A. 許可されていないIPから接続試行時QueryPieウェブコンソー
-![Each User設定のIPアクセス遮断時画面](/administrator-manual/general/company-management/security/image-20251218-082726.png) +Each User設定のIPアクセス遮断時画面
Each User設定のIPアクセス遮断時画面
-![All User設定のIPアクセス遮断時画面](/administrator-manual/general/company-management/security/image-20251212-162103.png) +All User設定のIPアクセス遮断時画面
All User設定のIPアクセス遮断時画面
@@ -161,7 +161,7 @@ Secret Store使用可否を設定します。 現在HashiCorp Vaultをサポートしています。
-![screenshot-20240726-152042.png](/administrator-manual/general/company-management/security/screenshot-20240726-152042.png) +screenshot-20240726-152042.png
Vault登録はGeneral > Integrationsメニューで実行します。 @@ -176,14 +176,14 @@ A. Administrator > General > Integrations > HashiCorp Valutメニュー Secret Store使用活性化およびVault登録が完了した後、DBコネクション詳細ページまたはServer Group詳細ページで認証情報保存庫を選択できるようになります。
-![DB Connection詳細ページ内Connection Information > Secret Store選択](/administrator-manual/general/company-management/security/screenshot-20240726-185946.png) +DB Connection詳細ページ内Connection Information > Secret Store選択
DB Connection詳細ページ内Connection Information > Secret Store選択
-![Server Group詳細ページ内Accounts > Secret Store選択](/administrator-manual/general/company-management/security/screenshot-20240726-190034.png) +Server Group詳細ページ内Accounts > Secret Store選択
Server Group詳細ページ内Accounts > Secret Store選択
@@ -198,7 +198,7 @@ Server Group詳細ページ内Accounts > Secret Store選択 その他セキュリティ設定を管理します。
-![screenshot-20240726-152051.png](/administrator-manual/general/company-management/security/screenshot-20240726-152051.png) +screenshot-20240726-152051.png
* Export a file with Encryption : ファイルダウンロード時パスワード入力可否 diff --git a/src/content/ja/administrator-manual/general/system/api-token.mdx b/src/content/ja/administrator-manual/general/system/api-token.mdx index 9de79f72..2ce02507 100644 --- a/src/content/ja/administrator-manual/general/system/api-token.mdx +++ b/src/content/ja/administrator-manual/general/system/api-token.mdx @@ -40,7 +40,7 @@ APIトークン使用時の注意事項は以下の通りです。 ### APIトークンリスト照会
-![Administrator > General > System > API Token](/administrator-manual/general/system/api-token/screenshot-20240723-110619.png) +Administrator > General > System > API Token
Administrator > General > System > API Token
@@ -56,7 +56,7 @@ Administrator > General > System > API Token ### APIトークン生成
-![Administrator > General > System > API Token > Create API Token](/administrator-manual/general/system/api-token/image-20241028-094955.png) +Administrator > General > System > API Token > Create API Token
Administrator > General > System > API Token > Create API Token
@@ -77,7 +77,7 @@ Administrator > General > System > API Token > Create API Token 3. `Ok`ボタンをクリックするとAPI Token生成が完了します。 4. 生成完了モーダルで初回に限りAPI Token情報を確認できます。
- ![General Settings > System > API Token > Create API Token](/administrator-manual/general/system/api-token/screenshot-20240723-120533.png) + General Settings > System > API Token > Create API Token
General Settings > System > API Token > Create API Token
@@ -89,7 +89,7 @@ Administrator > General > System > API Token > Create API Token ### APIトークン修正
-![General Settings > System > API Token > Edit API Token](/administrator-manual/general/system/api-token/image-20241028-095455.png) +General Settings > System > API Token > Edit API Token
General Settings > System > API Token > Edit API Token
@@ -121,7 +121,7 @@ General Settings > System > API Token > Edit API Token ### APIトークン削除
-![Administrator > General > System > API Token > Delete](/administrator-manual/general/system/api-token/screenshot-20240723-121212.png) +Administrator > General > System > API Token > Delete
Administrator > General > System > API Token > Delete
diff --git a/src/content/ja/administrator-manual/general/system/integrations.mdx b/src/content/ja/administrator-manual/general/system/integrations.mdx index c9c0279f..016d4748 100644 --- a/src/content/ja/administrator-manual/general/system/integrations.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations.mdx @@ -18,7 +18,7 @@ Integrationメニューでは外部セキュリティサービスとの連携を
-![Administrator > General > System > Integrations](/administrator-manual/general/system/integrations/image-20240714-054645.png) +Administrator > General > System > Integrations
Administrator > General > System > Integrations
diff --git a/src/content/ja/administrator-manual/general/system/integrations/identity-providers.mdx b/src/content/ja/administrator-manual/general/system/integrations/identity-providers.mdx index 7b69f57c..686e401f 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/identity-providers.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/identity-providers.mdx @@ -33,7 +33,7 @@ Admin > General > System > IntegrationのAuthentication下位項目にI この項目は削除できません。
-![image-20251014-010700.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-010700.png) +image-20251014-010700.png
#### 基本認証の詳細設定 @@ -43,7 +43,7 @@ Admin > General > System > IntegrationのAuthentication下位項目にI * **Multi-Factor Authentication Setting** : MFA設定を行うことができます。Google Authenticator、Emailをサポートします。
-![Internal databaseの詳細設定](/administrator-manual/general/system/integrations/identity-providers/image-20251014-011706.png) +Internal databaseの詳細設定
Internal databaseの詳細設定
@@ -65,7 +65,7 @@ IdPを変更または削除する必要がある場合は、Customer Portalを * **Bind Password** : BindDNのパスワードを入力します。
-![LDAP詳細設定](/administrator-manual/general/system/integrations/identity-providers/image-20251014-012049.png) +LDAP詳細設定
LDAP詳細設定
@@ -84,7 +84,7 @@ QueryPieユーザーアカウントとLDAPのユーザーアカウントを同 LDAPからユーザーグループ情報および所属情報を同期するには、**Use Groupオプション**を有効化（チェック）し、必須で指定された情報を入力します。
-![image-20251014-075227.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-075227.png) +image-20251014-075227.png
@@ -167,7 +167,7 @@ Membership Type LDAPサーバーからユーザー情報同期を実行する場合は、**Use Synchronization with the Authentication System**オプションを有効化します。
-![image-20251014-075127.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-075127.png) +image-20251014-075127.png
@@ -206,7 +206,7 @@ LDAPで管理中のユーザー属性をQueryPie内Attributeとマッピング Active DirectoryをLDAP連携する場合、Anonymous項目を必ずfalseに設定しなければなりません。 ADは基本的に匿名バインド状態での検索作業を許可しません。
-![image-20251222-023912.png](/administrator-manual/general/system/integrations/identity-providers/image-20251222-023912.png) +image-20251222-023912.png
@@ -215,7 +215,7 @@ ADは基本的に匿名バインド状態での検索作業を許可しません #### OktaでQueryPieをアプリケーションとして追加
-![Okta Admin > Applications > Applications > Browse App Catalog > QueryPie検索](/administrator-manual/general/system/integrations/identity-providers/image-20240723-064242.png) +Okta Admin > Applications > Applications > Browse App Catalog > QueryPie検索
Okta Admin > Applications > Applications > Browse App Catalog > QueryPie検索
@@ -231,7 +231,7 @@ Okta Admin > Applications > Applications > Browse App Catalog > Quer #### Oktaアカウント連携のためのProfile設定
-![Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute](/administrator-manual/general/system/integrations/identity-providers/image-20240723-064424.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
@@ -247,7 +247,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Add Attrib * Display name：loginId / Variable name：loginId項目入力後`Save`クリック
-![Okta Admin > Directory > Profile Editor > QueryPie User > Mappings](/administrator-manual/general/system/integrations/identity-providers/image-20240723-064721.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
@@ -265,7 +265,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Mappings #### Oktaに追加されたQueryPieアプリケーションにユーザー割り当て
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/system/integrations/identity-providers/image-20240723-065134.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -283,7 +283,7 @@ Okta Admin > Applications > Applications > QueryPie App #### OktaでQueryPieアプリケーション連携情報設定
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/system/integrations/identity-providers/image-20240723-065346.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -306,7 +306,7 @@ QueryPie-Okta間のユーザーおよびグループ、グループメンバー ただし、セキュリティレベル向上のためにOkta APIトークンの権限を最小限に付与するよう調整する必要がある場合は、以下の権限および方法に従ってAPIトークンを生成することを推奨します。
-![Okta Admin Console > Security > Administrators > Roles > Create new role](/administrator-manual/general/system/integrations/identity-providers/image-20240110-042233.png) +Okta Admin Console > Security > Administrators > Roles > Create new role
Okta Admin Console > Security > Administrators > Roles > Create new role
@@ -346,7 +346,7 @@ Okta Admin Console > Security > Administrators > Roles > Create new リスト右上の`+ Add`ボタンを押し、ポップアップされる画面でTypeをOktaに選択すると、OktaをIdPとして追加できます。
-![Okta詳細設定（1）](/administrator-manual/general/system/integrations/identity-providers/image-20251014-014729.png) +Okta詳細設定（1）
Okta詳細設定（1）
@@ -395,14 +395,14 @@ SPは各バインディング方式に従って別々のACS URLを運営でき 特定の状況やクライアントの要求に従って動的に生成されたACS URLにアサーションを受信する必要がある時、インデックスを通じて静的に定義された複数のURL中1つを選択するよう誘導できます。
-![okta app設定のAudience URI(SP Entity ID) ](/administrator-manual/general/system/integrations/identity-providers/screenshot-20250124-164255.png) +okta app設定のAudience URI(SP Entity ID)
okta app設定のAudience URI(SP Entity ID)
-![Other Requestable SSO URLsのIndex](/administrator-manual/general/system/integrations/identity-providers/screenshot-20250124-164553.png) +Other Requestable SSO URLsのIndex
Other Requestable SSO URLsのIndex
@@ -410,7 +410,7 @@ Other Requestable SSO URLsのIndex
-![Okta詳細設定（2）](/administrator-manual/general/system/integrations/identity-providers/image-20251014-014805.png) +Okta詳細設定（2）
Okta詳細設定（2）
@@ -440,7 +440,7 @@ Okta詳細設定（2）
-![Okta Admin > Applications > QueryPie App上部URL](/administrator-manual/general/system/integrations/identity-providers/Authentication-Okta-02.png) +Okta Admin > Applications > QueryPie App上部URL
Okta Admin > Applications > QueryPie App上部URL
@@ -453,7 +453,7 @@ Okta Admin > Applications > QueryPie App上部URL 2. これでログインページで`Login with Okta`ボタンを通じてOktaアカウントでQueryPieにログインできます。
-![image-20251014-082704.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-082704.png) +image-20251014-082704.png
@@ -485,7 +485,7 @@ One Login SAML Custom Connector設定に関する詳細内容は[https://onelogi * **Identity Provider Metadata** : One LoginでダウンロードしたXMLファイルの内容をコピーして貼り付けます。
-![One Login詳細設定（1）](/administrator-manual/general/system/integrations/identity-providers/image-20251020-001435.png) +One Login詳細設定（1）
One Login詳細設定（1）
@@ -495,7 +495,7 @@ One Login詳細設定（1） * 定期的な同期機能を使用したい場合はReplication Frequency項目でSchedulingを設定します。
-![One Login詳細設定（2）](/administrator-manual/general/system/integrations/identity-providers/image-20251014-014949.png) +One Login詳細設定（2）
One Login詳細設定（2）
@@ -520,7 +520,7 @@ One Login詳細設定（2） * **Identity Provider Metadata** : IdPで確認したSAML metadata XMLの内容をコピーして貼り付けます。
-![image-20251014-015015.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-015015.png) +image-20251014-015015.png
< 参考 > [AWS SSO連携](identity-providers/aws-sso-saml-20) @@ -535,7 +535,7 @@ Custom Identity Providerは認証APIサーバーを使用する特殊な場合 * ユーザー情報同期を実行したい場合はUse Synchronization with the Authentication Systemオプションを有効化します。
-![image-20251014-015047.png](/administrator-manual/general/system/integrations/identity-providers/image-20251014-015047.png) +image-20251014-015047.png
* **Additional Settings** diff --git a/src/content/ja/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx b/src/content/ja/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx index cf7c8658..a90304b0 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20.mdx @@ -18,7 +18,7 @@ QueryPieのIdentity Providers Integration設定でSAMLをTypeとして選択し ### AWS IAM Identity CenterでQueryPieをアプリケーションとして追加
-![AWS-SSO-01-20230317-044219.png](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/AWS-SSO-01-20230317-044219.png) +AWS-SSO-01-20230317-044219.png
1. [AWS IAM Identity Center](https://ap-northeast-2.console.aws.amazon.com/singlesignon/applications/home)にアクセスします。 @@ -37,7 +37,7 @@ QueryPieのIdentity Providers Integration設定でSAMLをTypeとして選択し ### QueryPie連携のための属性マッピング設定
-![AWS-SSO-06-20230317-064023.png](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/AWS-SSO-06-20230317-064023.png) +AWS-SSO-06-20230317-064023.png
1. 生成されたアプリケーション右上で作業 > 属性マッピング編集に移動します。 @@ -56,7 +56,7 @@ QueryPieのIdentity Providers Integration設定でSAMLをTypeとして選択し ### QueryPieでAWS IAM Identity Center連携設定
-![Administrator > General > User Management > Authentication ](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/image-20240723-072112.png) +Administrator > General > User Management > Authentication
Administrator > General > User Management > Authentication
@@ -72,7 +72,7 @@ Administrator > General > User Management > Authentication ### QueryPieでSAMLログイン
-![image-20251020-044838.png](/administrator-manual/general/system/integrations/identity-providers/integrating-with-aws-sso-saml-20/image-20251020-044838.png) +image-20251020-044838.png
ログインページで`Login with SAML`ボタンを通じてAWS認証してQueryPieにログインします。 diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx index d4f34bdc..5f03c112 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20.mdx @@ -11,7 +11,7 @@ Google Cloud APIで生成したClient IDおよびClient Secret情報を登録し ### Googl Cloud API Integration
-![OAuth 2.0認証を使用するためのGoogle Cloud API Integration](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-090507.png) +OAuth 2.0認証を使用するためのGoogle Cloud API Integration
OAuth 2.0認証を使用するためのGoogle Cloud API Integration
@@ -23,14 +23,14 @@ OAuth 2.0認証を使用するためのGoogle Cloud API Integration 2. Authentication項目下でGoogle Cloud APIタイルをクリックします。 3. OAuth 2.0 Client IDs項目の`+Add`ボタンをクリックします。
- ![Client ID追加](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-102818.png) + Client ID追加
Client ID追加
4. ポップアップウィンドウに情報を入力しSaveボタンを押して保存します。
- ![OAuth 2.0 Client ID情報入力](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-103102.png) + OAuth 2.0 Client ID情報入力
OAuth 2.0 Client ID情報入力
@@ -48,14 +48,14 @@ OAuth 2.0認証を使用するためのGoogle Cloud API Integration 1. リストで削除を希望する特定Client IDをチェックします。
- ![Client ID削除](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-110050.png) + Client ID削除
Client ID削除
2. 上部のDeleteボタンを押して削除します。
この時削除したいClient IDがコネクション設定と接続されていると以下のような警告メッセージが出力され削除できません。まずコネクション設定でOAuth設定を削除するかコネクションを削除する必要があります。
- ![接続でClient IDを使用中に削除を試みると警告表示](/administrator-manual/general/system/integrations/integrating-google-cloud-api-for-oauth-20/image-20250116-105240.png) + 接続でClient IDを使用中に削除を試みると警告表示
接続でClient IDを使用中に削除を試みると警告表示
diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-email.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-email.mdx index ff5ac207..d3ea4440 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-email.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-email.mdx @@ -22,7 +22,7 @@ Email送信にはSMTPサーバーが必要で、QueryPieではSMTPサーバー 2. Emailタイルをクリックして詳細ページに移動します。 3. 詳細ページにある`Configure`ボタンをクリックするとSMTP情報を入力できるポップアップが表示されます。

- ![Email Integration 상세페이지](/administrator-manual/general/system/integrations/integrating-with-email/image-20241218-163108.png) + Email Integration 상세페이지
Email Integration 상세페이지
@@ -43,7 +43,7 @@ Email送信にはSMTPサーバーが必要で、QueryPieではSMTPサーバー 11. **Testボタン** : SMTP設定が接続に問題ないか確認します。
12.
- ![SMTP 설정 팝업 다이얼로그](/administrator-manual/general/system/integrations/integrating-with-email/image-20241218-163449.png) + SMTP 설정 팝업 다이얼로그
SMTP 설정 팝업 다이얼로그
@@ -56,7 +56,7 @@ Email送信にはSMTPサーバーが必要で、QueryPieではSMTPサーバー 2. Emailタイルをクリックして詳細ページに移動します。 3. 詳細ページEmail senderに表示されたSMTP設定に対してEditボタンを押します。

- ![Email Sender](/administrator-manual/general/system/integrations/integrating-with-email/image-20241219-011621.png) + Email Sender
Email Sender
@@ -69,7 +69,7 @@ Email送信にはSMTPサーバーが必要で、QueryPieではSMTPサーバー 2. Emailタイルをクリックして詳細ページに移動します。 3. Sent Email Historyリストを確認します。
このリストに保存されるemail送信履歴は30日間保管され30日以前の内容は削除されます。

- ![Sent Email History](/administrator-manual/general/system/integrations/integrating-with-email/image-20241219-005544.png) + Sent Email History
Sent Email History
@@ -81,7 +81,7 @@ Email送信にはSMTPサーバーが必要で、QueryPieではSMTPサーバー 2. Emailタイルをクリックして詳細ページに移動します。 3. 詳細ページEmail senderに表示されたSMTP設定に対してDeleteボタンを押します。
SMTP設定を使用するAlert、MFAなどの設定が存在する場合SMTP設定を削除できません。
まず関連設定をすべて削除してから削除可能です。
- ![Email Sender](/administrator-manual/general/system/integrations/integrating-with-email/image-20241219-011621.png) + Email Sender
Email Sender
diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx index 164b4827..0fbed2ea 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-event-callback.mdx @@ -17,7 +17,7 @@ Event Callback連携はウェブフック（Webhook）を通じてQueryPieで発 3. 詳細ページにある`+ Create`ボタンをクリックするとEvent Callbackを生成できるポップアップが表示されます。
-![Event Callback Integration詳細ページ](/administrator-manual/general/system/integrations/integrating-with-event-callback/Screenshot-2025-08-25-at-6.04.50-PM.png) +Event Callback Integration詳細ページ
Event Callback Integration詳細ページ
@@ -38,7 +38,7 @@ Event Callback Integration詳細ページ * **Authorization Header** : ウェブフックリクエスト時セキュリティ認証のために必要な認証ヘッダー値を入力します。（例：Authorization: Bearer <token>） * **Description** : 設定に対する説明を入力します。（選択事項）
- ![Event Callback設定ポップアップダイアログ](/administrator-manual/general/system/integrations/integrating-with-event-callback/Screenshot-2025-08-25-at-6.06.50-PM.png) + Event Callback設定ポップアップダイアログ
Event Callback設定ポップアップダイアログ
@@ -61,6 +61,6 @@ Event Callback Integration詳細ページ 3. 生成されたEvent Callbackリストで削除したい項目の左側チェックボックスをチェックします。 4. リスト左上部で`Delete`ボタンをクリックします
- ![Screenshot-2025-08-25-at-6.14.27-PM.png](/administrator-manual/general/system/integrations/integrating-with-event-callback/Screenshot-2025-08-25-at-6.14.27-PM.png) + Screenshot-2025-08-25-at-6.14.27-PM.png
5. 確認ウィンドウが表示されると削除を進行して設定を削除します。 diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx index 14a04f4b..e6a93633 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-secret-store.mdx @@ -42,7 +42,7 @@ Secret Storeを通じて安全にDBおよびサーバー認証情報を管理で ### HashiCorp Vault連携情報照会
-![Administrator > General > System > Integrations > HashiCorp Vault](/administrator-manual/general/system/integrations/integrating-with-secret-store/screenshot-20240723-094426.png) +Administrator > General > System > Integrations > HashiCorp Vault
Administrator > General > System > Integrations > HashiCorp Vault
@@ -59,7 +59,7 @@ Administrator > General > Securityページ内Secret Store有効化を解 以下は連携情報を削除する方法です。
-![Administrator > General > System > Integrations > HashiCorp Vault > Delete](/administrator-manual/general/system/integrations/integrating-with-secret-store/screenshot-20240723-095912.png) +Administrator > General > System > Integrations > HashiCorp Vault > Delete
Administrator > General > System > Integrations > HashiCorp Vault > Delete
@@ -73,7 +73,7 @@ Administrator > General > System > Integrations > HashiCorp Vault &g ### HashiCorp Vault連携情報入力
-![Administrator > General > System > Integrations > HashiCorp Vault > Connect](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-05-27-at-11.37.33-AM.png) +Administrator > General > System > Integrations > HashiCorp Vault > Connect
Administrator > General > System > Integrations > HashiCorp Vault > Connect
@@ -111,7 +111,7 @@ Administrator > General > System > Integrations > HashiCorp Vault &g ### Active Directory連携情報照会
-![Administrator > General > System > Integrations > Microsoft Active Directory](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-07-22-at-11.32.23-AM.png) +Administrator > General > System > Integrations > Microsoft Active Directory
Administrator > General > System > Integrations > Microsoft Active Directory
@@ -125,7 +125,7 @@ Administrator > General > System > Integrations > Microsoft Active D ### Active Directory連携情報削除
-![Screenshot-2025-07-22-at-11.33.43-AM.png](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-07-22-at-11.33.43-AM.png) +Screenshot-2025-07-22-at-11.33.43-AM.png
1. 削除するAD情報のテーブル項目でチェックボックスを選択するとヘッダー領域に`Delete`ボタンが表示されます。該当ボタンをクリックします。 @@ -142,7 +142,7 @@ Admin > Servers> Account Management > Active Directoryタブで関連 ### Active Directory連携情報入力
-![Screenshot-2025-07-22-at-11.33.26-AM.png](/administrator-manual/general/system/integrations/integrating-with-secret-store/Screenshot-2025-07-22-at-11.33.26-AM.png) +Screenshot-2025-07-22-at-11.33.26-AM.png
1. Active Directoryページで`+ Connect`ボタンをクリックします。 diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx index a8f245dd..5e0c1fd8 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm.mdx @@ -27,15 +27,15 @@ App Manifestを利用してQueryPie DM連携専用Slack Appを生成します。 1. [https://api.slack.com/apps](https://api.slack.com/apps)に移動して`Create an App`をクリックします。

- ![image-20231227-065658.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20231227-065658.png) + image-20231227-065658.png
2. Create an appモーダルで、App生成方式を選択します。`From a manifest`をクリックします。

- ![screenshot-20250218-131725.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-131725.png) + screenshot-20250218-131725.png
3. Pick a workspaceモーダルでQueryPieと連携するSlack Workspaceを選択した後次の段階に進行します。

- ![image-20231227-065951.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20231227-065951.png) + image-20231227-065951.png
4. Create app from manifestモーダルでJSON形式のApp Manifestを入力します。
事前に埋められている内容を削除し以下のApp Manifestを貼り付けた後次の段階に進行します。
:light_bulb_on: `{{..}}`内の値は希望する値に変更してください。
``` @@ -70,7 +70,7 @@ App Manifestを利用してQueryPie DM連携専用Slack Appを生成します。 ``` 5. 設定内容を検討し`Create`ボタンをクリックしてApp生成を完了します。

- ![image-20240115-220447.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240115-220447.png) + image-20240115-220447.png
### Slack WorkspaceにSlack Appインストール @@ -78,11 +78,11 @@ App Manifestを利用してQueryPie DM連携専用Slack Appを生成します。 1. Settings > Install Appで`Install to Workspace`ボタンをクリックして生成されたアプリをSlack Workspaceにインストールします。 2. 権限リクエストページで、`許可`をクリックします。
- ![image-20240115-221520.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240115-221520.png) + image-20240115-221520.png
3. 設定したSlack WorkspaceでSlack DM専用Appが生成されたことを確認できます。
- ![image-20240115-221618.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240115-221618.png) + image-20240115-221618.png
### Bot User OAuth Token取得 @@ -90,7 +90,7 @@ App Manifestを利用してQueryPie DM連携専用Slack Appを生成します。 Features > OAuth & Permissionsメニュー内OAuth Tokens for Your Workspaceセクションで、**Bot User OAuth Token**をコピーして記録しておきます。
-![image-20240418-022640.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20240418-022640.png) +image-20240418-022640.png
@@ -106,11 +106,11 @@ App manifestでSlack appを生成する時Socket Modeと関連権限を有効化 1. アプリ設定ページのSettings > Basic InformationメニューのApp-Level Tokensセクションに移動し、`Generate Token and Scope`ボタンをクリックします。

- ![screenshot-20250218-140951.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-140951.png) + screenshot-20250218-140951.png
2. Generate an app-level tokenモーダルで、Add Scopeボタンをクリックした後`connections:write`を追加します。

- ![screenshot-20250218-141555.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-141555.png) + screenshot-20250218-141555.png
3. 生成されたApp-Level Tokenモーダルで、アプリトークンをコピーして別途記録しておきます。App-Level Tokenは`xapp-`で始まります。 @@ -118,7 +118,7 @@ App manifestでSlack appを生成する時Socket Modeと関連権限を有効化 1. Admin > General > System > Integrations > Slackメニューに進入した後、`Configure`ボタンをクリックして設定モーダルを開きます。

- ![Administrator > General > System > Integrations > Slack > Create a New Slack Configuration](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250310-113509.png) + Administrator > General > System > Integrations > Slack > Create a New Slack Configuration
Administrator > General > System > Integrations > Slack > Create a New Slack Configuration
@@ -128,7 +128,7 @@ App manifestでSlack appを生成する時Socket Modeと関連権限を有効化 * **Send Workflow Notification via Slack DM** : ワークフローリクエストに対するSlack DM送信有効化 * **Allow Users to approve or reject on Slack DM** : Slack DM内で承認または拒否機能有効化

- ![アクション許容タイプ例（左）/ アクション非許容タイプ例（右）](/administrator-manual/general/system/integrations/integrating-with-slack-dm/image-20231003-054240.png) + アクション許容タイプ例（左）/ アクション非許容タイプ例（右）
アクション許容タイプ例（左）/ アクション非許容タイプ例（右）
@@ -139,14 +139,14 @@ App manifestでSlack appを生成する時Socket Modeと関連権限を有効化 1. Slack Configurationを登録した後、現在の設定状態を画面で確認できます。

- ![Administrator > General > System > Integrations > Slack](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250310-113950.png) + Administrator > General > System > Integrations > Slack
Administrator > General > System > Integrations > Slack
2. `Edit`ボタンをクリックして入力した設定を変更できます。
- ![Administrator > General > System > Integrations > Slack > Edit the Slack Configuration](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-152840.png) + Administrator > General > System > Integrations > Slack > Edit the Slack Configuration
Administrator > General > System > Integrations > Slack > Edit the Slack Configuration
@@ -159,13 +159,13 @@ DB Access Requestを例に、Slack DM機能が正常に動作するかテスト 1. QueryPie User > WorkflowページでSubmit Requestボタンをクリックした後、DB Access Requestを選択してリクエスト作成画面に進入します。リクエスト作成画面で必要な情報を入力し、リクエストを提出します。
- ![screenshot-20250218-151504.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-151504.png) + screenshot-20250218-151504.png
2. 承認者は前に追加したSlack AppとのDMで承認すべきリクエスト通知を受信できます。
**Allow Users to approve or reject on Slack DM**設定がオンになっているため、DMで直接理由を入力してリクエストを承認または拒否できます。

- ![screenshot-20250218-152238.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-152238.png) + screenshot-20250218-152238.png
3. DMで`Details`ボタンをクリック時、QueryPie Adminで承認リクエストに対する詳細内容を確認し承認または拒否できます。
- ![screenshot-20250218-152527.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/screenshot-20250218-152527.png) + screenshot-20250218-152527.png
diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx index 18fef16f..93ad11bf 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types.mdx @@ -44,7 +44,7 @@ QueryPie管理者の事前設定により、メッセージを受信した承認 事後承認リクエスト件であるため、アクションボタンを使用中でも`Approve`ボタンのみ表示されます。
-![一般モード承認リクエスト例（左）/ 事後承認モード承認リクエスト例（右）](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-062427.png) +一般モード承認リクエスト例（左）/ 事後承認モード承認リクエスト例（右）
一般モード承認リクエスト例（左）/ 事後承認モード承認リクエスト例（右）
@@ -53,7 +53,7 @@ QueryPie管理者の事前設定により、メッセージを受信した承認 ### 却下通知
-![image-20231003-060544.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-060544.png) +image-20231003-060544.png
Workflowの4つのタイプ（SQL Request、SQL Export Request、DB Access Request、Server Access Request）すべてをサポートします。 @@ -70,7 +70,7 @@ Workflowの4つのタイプ（SQL Request、SQL Export Request、DB Access Reque ### 承認完了通知 - リクエスト者に
-![image-20231003-060552.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-060552.png) +image-20231003-060552.png
Workflowの4つのタイプ（SQL Request、SQL Export Request、DB Access Request、Server Access Request）すべてをサポートします。 @@ -96,13 +96,13 @@ WorkflowでExecute行動を含む2つのタイプ（SQL Request、SQL Export Req 事後承認（Urgent Mode）起案の場合には起案提出即座に実行者にメッセージが送信されます。
-![image-20231003-062055.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-062055.png) +image-20231003-062055.png
### Urgent Mode未承認通知
-![image-20231003-062615.png](/administrator-manual/general/system/integrations/integrating-with-slack-dm/slack-dm-workflow-notification-types/image-20231003-062615.png) +image-20231003-062615.png
Workflowで2つのタイプ（SQL Request、SQL Export Request）をサポートします。 diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-splunk.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-splunk.mdx index f3581d0d..41128d4a 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-splunk.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-splunk.mdx @@ -18,7 +18,7 @@ Integration設定にはSystem admin権限が必要です。 ### Syslog-Splunk連携推奨アーキテクチャ
-![Splunk連携推奨アーキテクチャ](/administrator-manual/general/system/integrations/integrating-with-splunk/screenshot-20240613-174947.png) +Splunk連携推奨アーキテクチャ
Splunk連携推奨アーキテクチャ
@@ -43,7 +43,7 @@ QueryPieは顧客便宜のためTCP、UDP、HTTP、HTTPSプロトコルを使用 3. 詳細ページにある`Configure`ボタンをクリックすると以下のようにDestination情報を入力できるポップアップが表示されます。
-![（左）TCP / UDP設定画面 （右）HTTP / HTTPS設定画面](/administrator-manual/general/system/integrations/integrating-with-splunk/image-20240523-101104.png) +（左）TCP / UDP設定画面 （右）HTTP / HTTPS設定画面
（左）TCP / UDP設定画面 （右）HTTP / HTTPS設定画面
@@ -84,7 +84,7 @@ QueryPieは顧客便宜のためTCP、UDP、HTTP、HTTPSプロトコルを使用
-![image-20251009-045210.png](/administrator-manual/general/system/integrations/integrating-with-splunk/image-20251009-045210.png) +image-20251009-045210.png
diff --git a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-syslog.mdx b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-syslog.mdx index d938bc66..a3182d92 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/integrating-with-syslog.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/integrating-with-syslog.mdx @@ -29,7 +29,7 @@ Legacy FormatはSyslogプロトコル上TimestampフィールドがTime Zoneの 1. 詳細ページにある`Configure`ボタンをクリックするとDestination情報を入力できるポップアップが表示されます。
-![Administrator > General > System > Integrations > Syslog > Configure Destination](/administrator-manual/general/system/integrations/integrating-with-syslog/screenshot-20240723-093628.png) +Administrator > General > System > Integrations > Syslog > Configure Destination
Administrator > General > System > Integrations > Syslog > Configure Destination
@@ -60,7 +60,7 @@ Administrator > General > System > Integrations > Syslog > Config
-![image-20251009-045004.png](/administrator-manual/general/system/integrations/integrating-with-syslog/image-20251009-045004.png) +image-20251009-045004.png
diff --git a/src/content/ja/administrator-manual/general/system/integrations/oauth-client-application.mdx b/src/content/ja/administrator-manual/general/system/integrations/oauth-client-application.mdx index 377aa765..917c47f0 100644 --- a/src/content/ja/administrator-manual/general/system/integrations/oauth-client-application.mdx +++ b/src/content/ja/administrator-manual/general/system/integrations/oauth-client-application.mdx @@ -12,7 +12,7 @@ title: 'OAuth Client Application' ### OAuth Client Application登録
-![Admin > General > System > IntegrationsのAuthentication下位にあるOAuth Client Application](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-041209.png) +Admin > General > System > IntegrationsのAuthentication下位にあるOAuth Client Application
Admin > General > System > IntegrationsのAuthentication下位にあるOAuth Client Application
@@ -26,7 +26,7 @@ Admin > General > System > IntegrationsのAuthentication下位にある * **Refresh Token Timeout (Minutes)** : 基本値は1440、最小値は5です。
-![Add OAuth Client Application](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-043210.png) +Add OAuth Client Application
Add OAuth Client Application
@@ -36,7 +36,7 @@ Add OAuth Client Application * 設定が保存された後出力されるポップアップでClient IDとClient Secretが出力されます。Client Secretは最初に生成された値を再確認できないため、コピーしてよく保管する必要があります。
-![Client IDおよびClient Secret](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-043334.png) +Client IDおよびClient Secret
Client IDおよびClient Secret
@@ -45,7 +45,7 @@ Client IDおよびClient Secret ### OAuth Client Application設定修正
-![OAuth Client Application設定修正](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-044214.png) +OAuth Client Application設定修正
OAuth Client Application設定修正
@@ -61,7 +61,7 @@ OAuth Client Applicationリストで行をクリックすると以下の作業 登録するOAuth Client Application設定を削除するには、リストで削除対象項目をチェックして`Delete`ボタンを押します。
-![OAuth Client Application設定削除](/administrator-manual/general/system/integrations/oauth-client-application/image-20251009-044400.png) +OAuth Client Application設定削除
OAuth Client Application設定削除
diff --git a/src/content/ja/administrator-manual/general/system/jobs.mdx b/src/content/ja/administrator-manual/general/system/jobs.mdx index 75c6190f..880ac7b3 100644 --- a/src/content/ja/administrator-manual/general/system/jobs.mdx +++ b/src/content/ja/administrator-manual/general/system/jobs.mdx @@ -11,7 +11,7 @@ import { Callout } from 'nextra/components' QueryPieシステム上で周期的または手動で実行される多様な作業を一覧するメニューです。
-![Administrator > General > System > Jobs](/administrator-manual/general/system/jobs/screenshot-20241107-223755.png) +Administrator > General > System > Jobs
Administrator > General > System > Jobs
@@ -52,7 +52,7 @@ Administrator > General > System > Jobsメニューに進入してJobs
-![Administrator > General > System > Jobs > List Detail](/administrator-manual/general/system/jobs/screenshot-20241107-223800.png) +Administrator > General > System > Jobs > List Detail
Administrator > General > System > Jobs > List Detail
@@ -83,7 +83,7 @@ Administrator > General > System > Jobs > List Detail ### Job History照会
-![Administrator > General > System > Jobs > List Detail > History Detail](/administrator-manual/general/system/jobs/screenshot-20241107-223901.png) +Administrator > General > System > Jobs > List Detail > History Detail
Administrator > General > System > Jobs > List Detail > History Detail
diff --git a/src/content/ja/administrator-manual/general/system/maintenance.mdx b/src/content/ja/administrator-manual/general/system/maintenance.mdx index acc96eff..0bf88638 100644 --- a/src/content/ja/administrator-manual/general/system/maintenance.mdx +++ b/src/content/ja/administrator-manual/general/system/maintenance.mdx @@ -32,7 +32,7 @@ QueryPieのバージョンアップグレード作業を行う場合、QueryPie
-![Admin > General > System > Maintenance](/administrator-manual/general/system/maintenance/image-20250928-205515.png) +Admin > General > System > Maintenance
Admin > General > System > Maintenance
diff --git a/src/content/ja/administrator-manual/general/user-management.mdx b/src/content/ja/administrator-manual/general/user-management.mdx index eaaa97a7..1c03ac71 100644 --- a/src/content/ja/administrator-manual/general/user-management.mdx +++ b/src/content/ja/administrator-manual/general/user-management.mdx @@ -9,7 +9,7 @@ title: 'User Management' User Managementメニューでは、QueryPieのユーザー、管理者およびユーザーグループを管理できる様々な機能を提供します。
-![Administrator > General > Company Management > Security](/administrator-manual/general/user-management/screenshot-20240726-175124.png) +Administrator > General > Company Management > Security
Administrator > General > Company Management > Security
diff --git a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx index 6c84b33c..8fa12c11 100644 --- a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx +++ b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-aws-sso.mdx @@ -12,7 +12,7 @@ QueryPieではAWS IAM Identity Centerのユーザーを複数のクラウドア ### AWS IAM Identity CenterでQueryPieをアプリケーションとして追加
-![AWS-SSO-01-20230317-044219.png](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/AWS-SSO-01-20230317-044219.png) +AWS-SSO-01-20230317-044219.png
1. [AWS IAM Identity Center](https://ap-northeast-2.console.aws.amazon.com/singlesignon/applications/home)にアクセスします。 @@ -31,7 +31,7 @@ QueryPieではAWS IAM Identity Centerのユーザーを複数のクラウドア ### QueryPie連携のための属性マッピング設定
-![AWS-SSO-06-20230317-064023.png](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/AWS-SSO-06-20230317-064023.png) +AWS-SSO-06-20230317-064023.png
1. 生成されたアプリケーション右上で作業 > 属性マッピング編集に移動します。 @@ -50,7 +50,7 @@ QueryPieではAWS IAM Identity Centerのユーザーを複数のクラウドア ### QueryPieでAWS IAM Identity Center連携設定
-![Administrator > General > User Management > Authentication ](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/image-20240723-072112.png) +Administrator > General > User Management > Authentication
Administrator > General > User Management > Authentication
@@ -65,7 +65,7 @@ Administrator > General > User Management > Authentication ### QueryPieでSAMLログイン
-![image-20240723-073353.png](/administrator-manual/general/user-management/authentication/integrating-with-aws-sso/image-20240723-073353.png) +image-20240723-073353.png
これでログインページで`Login with SAML`ボタンを通じてAWS認証してQueryPieにログインできます。 diff --git a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx index 9b3d2b16..a25a428e 100644 --- a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx +++ b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-google-saml.mdx @@ -15,14 +15,14 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を 1. Google管理コンソールホームページにアクセス後左側メニューでアプリ > `ウェブおよびモバイルアプリ`をクリックします。
-![screenshot-20240902-162650.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-162650.png) +screenshot-20240902-162650.png
2. `アプリ追加`ボタンを押した後`カスタムSAMLアプリ追加`をクリックします。
-![image-20240902-073821.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/image-20240902-073821.png) +image-20240902-073821.png
@@ -30,7 +30,7 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を アプリ名項目に'QueryPie-SSO'を入力後`続行`ボタンをクリックします。
-![screenshot-20240902-164038.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164038.png) +screenshot-20240902-164038.png
@@ -38,7 +38,7 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を 入力完了後`続行`ボタンをクリックして3段階に移動します。
-![screenshot-20240902-164356.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164356.png) +screenshot-20240902-164356.png
* ACS URL : `https://{QueryPie Host}/saml/sp/acs` @@ -49,7 +49,7 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を 5. 3段階ページでは`マッチング追加`ボタンをクリックして以下の4つの値をすべて入力後`完了`ボタンをクリックします。
-![screenshot-20240902-164739.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164739.png) +screenshot-20240902-164739.png
* Basic Information : Primary email → email @@ -61,7 +61,7 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を 6. Google本人認証のためのパスワードを入力後`次`をクリックすると生成が完了します。
-![screenshot-20240902-164955.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-164955.png) +screenshot-20240902-164955.png
@@ -69,21 +69,21 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を 使用設定のために該当アプリをクリックします。
-![screenshot-20240902-165202.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-165202.png) +screenshot-20240902-165202.png
8. アプリの詳細情報で`メタデータダウンロード`をクリックしてファイルをダウンロードした後`ユーザーアクセス`項目をクリックします。
-![screenshot-20240902-165512.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-165512.png) +screenshot-20240902-165512.png
9. サービス状態を'すべてのユーザーに使用するよう設定'を選択した状態で`保存`ボタンをクリックします。
-![screenshot-20240902-165647.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-165647.png) +screenshot-20240902-165647.png
@@ -92,7 +92,7 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を 1. QueryPie Admin > General > User Management > Authenticationメニューに進入して以下のように設定します。
-![screenshot-20240902-170029.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/screenshot-20240902-170029.png) +screenshot-20240902-170029.png
* Type : SAMLを選択します。 @@ -103,7 +103,7 @@ QueryPieではGoogleのユーザーをSAML 2.0を通じてユーザー連携を ### QueryPieでSAMLログイン
-![image-20240723-073353.png](/administrator-manual/general/user-management/authentication/integrating-with-google-saml/image-20240723-073353.png) +image-20240723-073353.png
これでログインページで`Login with SAML`ボタンを通じてGoogleで認証してQueryPieにログインできます。 diff --git a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx index c1520044..ca0c54ef 100644 --- a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx +++ b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-ldap.mdx @@ -20,7 +20,7 @@ Administrator > General > User Management > Authenticationメニュー
-![Administrator > General > User Management > Authentication > LDAP](/administrator-manual/general/user-management/authentication/integrating-with-ldap/screenshot-20241209-203250.png) +Administrator > General > User Management > Authentication > LDAP
Administrator > General > User Management > Authentication > LDAP
@@ -29,7 +29,7 @@ Administrator > General > User Management > Authentication > LDAP #### 基本ユーザー連携設定
-![image-20250515-095143.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20250515-095143.png) +image-20250515-095143.png
LDAP連携のための基本的な認証情報および属性情報を入力します。 @@ -39,7 +39,7 @@ Attributeマッピングのための属性情報の場合、フィールド名 #### グループ連携設定
-![image-20250515-095109.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20250515-095109.png) +image-20250515-095109.png
LDAPでユーザーグループ情報および所属情報を同期するには **Use Groupオプション** を有効化し必須で指定された情報を入力します。 @@ -125,7 +125,7 @@ Group ID LDAPサーバーからユーザー情報同期を実行するには**Use Synchronization with the Authentication System**オプションを有効化します。
-![image-20250515-095420.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20250515-095420.png) +image-20250515-095420.png
* **Replication Frequency** : 自動同期機能使用可否を設定します。 @@ -227,7 +227,7 @@ QueryPie Attribute * **Dry Run :** `Dry Run`ボタンをクリックすると現在入力された設定情報を基盤に同期を実行する場合、その結果を事前に確認できます。（現在入力された情報の保存可否と無関係） * `Save Changes`をクリックすると入力された設定情報をQueryPieに保存します。 * `Synchronize`ボタンをクリックすると現在入力された設定情報を基盤に同期を実行します。（現在入力した設定情報を保存した後にのみ有効化される） - * ![image-20241209-124345.png](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20241209-124345.png)ボタンをクリックすると直前の同期履歴を照会できます。 + * image-20241209-124345.png버튼을 클릭하면 직전의 동기화 이력을 조회할 수 있습니다. * 個別同期中失敗件がある場合、Progress Bar色が黄色で表示されます。 * 失敗ログは ❌ アイコンで表示されます。ログをクリックすると詳細なエラーメッセージを確認できます。 @@ -243,14 +243,14 @@ QueryPie Attribute 1. Administrator > General > User Management > UsersまたはGroupsメニューで同期されたユーザーおよびグループを確認できます。
- ![Admin > General > User Management > Users](/administrator-manual/general/user-management/authentication/integrating-with-ldap/screenshot-20241209-215940.png) + Admin > General > User Management > Users
Admin > General > User Management > Users
2. これでログインページでIDおよびPassword項目にLDAP認証情報を入力後ログインできます。
- ![QueryPie Log In](/administrator-manual/general/user-management/authentication/integrating-with-ldap/image-20240723-063737.png) + QueryPie Log In
QueryPie Log In
diff --git a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx index 4a4fb8dc..68aa1462 100644 --- a/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx +++ b/src/content/ja/administrator-manual/general/user-management/authentication/integrating-with-okta.mdx @@ -20,7 +20,7 @@ SCIMプロビジョニング連携まで実装したい場合、[[Okta] プロ ### OktaでQueryPieをアプリケーションとして追加
-![Okta Admin > Applications > Applications > Browse App Catalog > QueryPie検索](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-064242.png) +Okta Admin > Applications > Applications > Browse App Catalog > QueryPie検索
Okta Admin > Applications > Applications > Browse App Catalog > QueryPie検索
@@ -37,7 +37,7 @@ Okta Admin > Applications > Applications > Browse App Catalog > Quer ### Oktaアカウント連携のためのProfile設定
-![Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-064424.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
Okta Admin > Directory > Profile Editor > QueryPie User > Add Attribute
@@ -53,7 +53,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Add Attrib 4. Display name : loginId / Variable name : loginId項目入力後`Save`クリック
-![Okta Admin > Directory > Profile Editor > QueryPie User > Mappings](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-064721.png) +Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
Okta Admin > Directory > Profile Editor > QueryPie User > Mappings
@@ -71,7 +71,7 @@ Okta Admin > Directory > Profile Editor > QueryPie User > Mappings ### Oktaに追加されたQueryPieアプリケーションにユーザー割り当て
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-065134.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -89,7 +89,7 @@ Okta Admin > Applications > Applications > QueryPie App ### OktaでQueryPieアプリケーション連携情報設定
-![Okta Admin > Applications > Applications > QueryPie App](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-065346.png) +Okta Admin > Applications > Applications > QueryPie App
Okta Admin > Applications > Applications > QueryPie App
@@ -112,7 +112,7 @@ QueryPie-Okta間ユーザーおよびグループ、グループメンバーシ ただし、セキュリティレベル向上のためにOkta APIトークンの権限を最小限に付与するよう調整する必要がある場合、以下の権限および方法によりAPIトークンを生成することを推奨します。
-![Okta Admin Console > Security > Administrators > Roles > Create new role](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240110-042233.png) +Okta Admin Console > Security > Administrators > Roles > Create new role
Okta Admin Console > Security > Administrators > Roles > Create new role
@@ -151,7 +151,7 @@ Okta Admin Console > Security > Administrators > Roles > Create new ### QueryPieでOkta連携および同期設定
-![Administrator > General > User Management > Authentication](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20241103-071714.png) +Administrator > General > User Management > Authentication
Administrator > General > User Management > Authentication
@@ -176,7 +176,7 @@ Administrator > General > User Management > Authentication
-![Okta Admin > Applications > QueryPie App上部URL](/administrator-manual/general/user-management/authentication/integrating-with-okta/Authentication-Okta-02.png) +Okta Admin > Applications > QueryPie App上部URL
Okta Admin > Applications > QueryPie App上部URL
@@ -189,7 +189,7 @@ Okta Admin > Applications > QueryPie App上部URL 2. これでログインページで`Login with Okta`ボタンを通じてOktaアカウントでQueryPieにログインできます。
-![image-20240723-070449.png](/administrator-manual/general/user-management/authentication/integrating-with-okta/image-20240723-070449.png) +image-20240723-070449.png
diff --git a/src/content/ja/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx b/src/content/ja/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx index 404c00bb..db074e80 100644 --- a/src/content/ja/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx +++ b/src/content/ja/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication.mdx @@ -23,14 +23,14 @@ MFA手段を指定するにはAuthentication TypeがInternal databaseまたはLD * Admin > General > User Management > Authenticationに移動します。 * Authentication TypeがInternal databaseの場合

- ![Authentication Type - Internal Databaseの場合MFA設定](/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication/image-20241219-015811.png) + Authentication Type - Internal Databaseの場合MFA設定
Authentication Type - Internal Databaseの場合MFA設定
* Authentication TypeがLDAPの場合


- ![Authentication Type - LDAPの場合MFA設定](/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication/image-20241219-020050.png) + Authentication Type - LDAPの場合MFA設定
Authentication Type - LDAPの場合MFA設定
@@ -45,7 +45,7 @@ MFA手段を指定するにはAuthentication TypeがInternal databaseまたはLD * Admin > General > Company Management > Securityに移動します。 * Server Connection Security項目下のAccess Server with MFAを"Enable"に設定しMFA TypeをGoogle OTPまたはEmailを選択します。（Access Server with MFAはデフォルト値がDisableです。

- ![image-20241219-021137.png](/administrator-manual/general/user-management/authentication/setting-up-multi-factor-authentication/image-20241219-021137.png) + image-20241219-021137.png
diff --git a/src/content/ja/administrator-manual/general/user-management/groups.mdx b/src/content/ja/administrator-manual/general/user-management/groups.mdx index 81736a9c..da33b046 100644 --- a/src/content/ja/administrator-manual/general/user-management/groups.mdx +++ b/src/content/ja/administrator-manual/general/user-management/groups.mdx @@ -20,7 +20,7 @@ Administrator > General > User Management > Groupsページに進入す 照会可能な情報は以下の通りです。
-![Administrator > General > User Management > Groups](/administrator-manual/general/user-management/groups/image-20240714-053938.png) +Administrator > General > User Management > Groups
Administrator > General > User Management > Groups
@@ -50,7 +50,7 @@ Groupsページ右上`Create Group`ボタンをクリックするとモーダル リストでユーザーを追加しようとするグループをクリックするとDrawerが開き、詳細情報を確認できます。
-![Administrator > General > User Management > Groups > 詳細情報](/administrator-manual/general/user-management/groups/screenshot-20240726-121151.png) +Administrator > General > User Management > Groups > 詳細情報
Administrator > General > User Management > Groups > 詳細情報
@@ -62,7 +62,7 @@ Administrator > General > User Management > Groups > 詳細情報 3. 追加しようとするユーザーをクリックすると追加状態に変更されます。 4. 下部`Check all`ボタンをクリックすると全体ユーザーが選択されます。
- ![グループにユーザー追加](/administrator-manual/general/user-management/groups/image-20251009-050919.png) + グループにユーザー追加
グループにユーザー追加
@@ -83,7 +83,7 @@ Usersページでユーザーのアカウント状態がInactiveか確認して 3. ユーザー除去が完了するとDrawer内ユーザーリストおよびGroupリストの目録で確認できます。
-![Administrator > General > User Management > Groups > 詳細情報](/administrator-manual/general/user-management/groups/screenshot-20240726-122800.png) +Administrator > General > User Management > Groups > 詳細情報
Administrator > General > User Management > Groups > 詳細情報
@@ -96,7 +96,7 @@ Administrator > General > User Management > Groups > 詳細情報 グループ名を変更後`Save`ボタンをクリックして保存します。
-![Administrator > General > User Management > Groups > 詳細情報 > Update Group](/administrator-manual/general/user-management/groups/screenshot-20240726-122036.png) +Administrator > General > User Management > Groups > 詳細情報 > Update Group
Administrator > General > User Management > Groups > 詳細情報 > Update Group
@@ -110,7 +110,7 @@ Groupsリストで削除しようとするグループをチェックボック ボタンをクリックし、確認モーダルで`OK`ボタンをクリックして削除を完了します。
-![screenshot-20240726-123314.png](/administrator-manual/general/user-management/groups/screenshot-20240726-123314.png) +screenshot-20240726-123314.png
diff --git a/src/content/ja/administrator-manual/general/user-management/profile-editor.mdx b/src/content/ja/administrator-manual/general/user-management/profile-editor.mdx index 8b67f326..b0c3c498 100644 --- a/src/content/ja/administrator-manual/general/user-management/profile-editor.mdx +++ b/src/content/ja/administrator-manual/general/user-management/profile-editor.mdx @@ -14,7 +14,7 @@ Profile Editorを通じて、ユーザーの各属性別に台帳主体を設定 これを通じて、各組織のポリシーに合わせた柔軟なユーザー情報管理が可能です。
-![Screenshot-2025-05-09-at-2.04.57-PM.png](/administrator-manual/general/user-management/profile-editor/Screenshot-2025-05-09-at-2.04.57-PM.png) +Screenshot-2025-05-09-at-2.04.57-PM.png
### ユーザー属性主体設定定義 diff --git a/src/content/ja/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx b/src/content/ja/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx index c128119a..0cdcc327 100644 --- a/src/content/ja/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx +++ b/src/content/ja/administrator-manual/general/user-management/profile-editor/custom-attribute.mdx @@ -12,24 +12,24 @@ title: 'Custom Attribute' 1. 属性リストテーブル右上の`+ Create Attribute`ボタンをクリックします。
- ![Administrator > General > User Management > Profile Editor](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.04.57-PM.png) + Administrator > General > User Management > Profile Editor
Administrator > General > User Management > Profile Editor
2. 以下に明示された項目を入力後、`OK`ボタンを押してCustom Attributeを生成します。
- ![Screenshot-2025-05-09-at-2.23.22-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.23.22-PM.png) + Screenshot-2025-05-09-at-2.23.22-PM.png
* **Display Name** （必須）：属性の名前で重複できません。例）Team Leader * Display Name重複時には以下のようなエラーメッセージがモーダルで表示されます。
- ![Screenshot-2025-05-09-at-2.43.56-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.43.56-PM.png) + Screenshot-2025-05-09-at-2.43.56-PM.png
* **Variable Name** （必須）：属性の変数名で重複できません。例）teamLeader * Variable Name重複時には以下のようなエラーメッセージがモーダルで表示されます。
- ![Screenshot-2025-05-09-at-2.45.22-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.45.22-PM.png) + Screenshot-2025-05-09-at-2.45.22-PM.png
* **Datatype** （必須）：属性値のデータタイプを選択します。 * string：一般的なテキスト（文字列）値です。（例：「Marketing Team」） @@ -62,7 +62,7 @@ title: 'Custom Attribute' 1. 削除方法：
- ![Screenshot-2025-05-09-at-2.36.41-PM.png](/administrator-manual/general/user-management/profile-editor/custom-attribute/Screenshot-2025-05-09-at-2.36.41-PM.png) + Screenshot-2025-05-09-at-2.36.41-PM.png
* 削除するCustom Attribute項目のチェックボックスを選択します。 * テーブル上部に現れる`Delete`ボタンをクリックします。 diff --git a/src/content/ja/administrator-manual/general/user-management/provisioning.mdx b/src/content/ja/administrator-manual/general/user-management/provisioning.mdx index 0a5af1cd..e15fc3c2 100644 --- a/src/content/ja/administrator-manual/general/user-management/provisioning.mdx +++ b/src/content/ja/administrator-manual/general/user-management/provisioning.mdx @@ -10,7 +10,7 @@ title: 'Provisioning' 組織で使用するアカウントシステムを連動させて、組織内のユーザーおよびグループに該当するAttribute（属性）および現況をアカウントシステムで反映された即座にQueryPieに同期できます。
-![screenshot-20240613-174843.png](/administrator-manual/general/user-management/provisioning/screenshot-20240613-174843.png) +screenshot-20240613-174843.png
@@ -20,7 +20,7 @@ QueryPieでは、Auth Providerというフィールドを基にユーザーの 該当Auth Providerは、Administrator > General > User Management > Authenticationメニューで設定した外部アカウントシステムタイプに従います。
-![Administrator > General > User Management > Provisioning](/administrator-manual/general/user-management/provisioning/image-20240714-054222.png) +Administrator > General > User Management > Provisioning
Administrator > General > User Management > Provisioning
diff --git a/src/content/ja/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx b/src/content/ja/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx index 2a982765..a1c7909b 100644 --- a/src/content/ja/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx +++ b/src/content/ja/administrator-manual/general/user-management/provisioning/activating-provisioning.mdx @@ -22,7 +22,7 @@ SCIM 2.0プロトコルを基に動作するQueryPieのProvisioning機能は、 ### QueryPie Provisioning有効化
-![Administrator > General > User Management > Provisioning](/administrator-manual/general/user-management/provisioning/activating-provisioning/image-20240714-054222.png) +Administrator > General > User Management > Provisioning
Administrator > General > User Management > Provisioning
diff --git a/src/content/ja/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx b/src/content/ja/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx index b94b127f..9590928f 100644 --- a/src/content/ja/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx +++ b/src/content/ja/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide.mdx @@ -40,7 +40,7 @@ ______ #### OktaカスタムSCIMアプリ生成
-![Okta Admin Console > Applications > Applications > Create App Integration > SAML 2.0 > Configure SAML](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240723-050205.png) +Okta Admin Console > Applications > Applications > Create App Integration > SAML 2.0 > Configure SAML
Okta Admin Console > Applications > Applications > Create App Integration > SAML 2.0 > Configure SAML
@@ -73,7 +73,7 @@ ______ #### Okta-QueryPie Provisioning連動
-![Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > Integration](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240723-054522.png) +Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > Integration
Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > Integration
@@ -98,7 +98,7 @@ Okta Admin Console > Applications > Applications > Custom SCIM App > 3. Test Connector Configurationボタンを押して接続テストを進行します。 4. 「*Connector configured successfully*」文句と共にポップアップが現れると、`Close`ボタンをクリックします。
- ![image-20240430-025059.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-025059.png) + image-20240430-025059.png
5. 下部の`Save`ボタンを押して接続設定を保存します。 @@ -108,7 +108,7 @@ ______ #### SCIM API有効化およびチェック
-![Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > To App](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-034915.png) +Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > To App
Okta Admin Console > Applications > Applications > Custom SCIM App > Provisioning > To App
@@ -147,36 +147,36 @@ QueryPieプロファイル内のstaticIp、macAddressなど一部attribute項目 1. SCIMアプリのProvisioningタブ > To App下部の`Go to Profile Editor`をクリックします。
- ![image-20240712-082412.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082412.png) + image-20240712-082412.png
2. `Add Attribute`ボタンをクリックします。
- ![image-20240712-082549.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082549.png) + image-20240712-082549.png
3. 同期に必要なAttributeを新たに登録します。
- ![image-20240712-082453.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082453.png) + image-20240712-082453.png
1. Data type：QueryPieと同様にstringを選択します。 2. Display name：Okta内表記する属性名を記入します。 3. Variable name & External name：同期するcustom attribute変数名を記入します。 * QueryPieユーザープロファイルでも括弧で変数名確認が可能です。
- ![image-20240712-083117.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-083117.png) + image-20240712-083117.png
4. External namespace：以下の値を記入します。
`urn:ietf:params:scim:schemas:extension:querypie:2.0:User` 5. 以降`Save`または`Save and Add Another`ボタンをクリックして保存します。 4. 次に`Mappings`ボタンをクリックします。
- ![image-20240712-082549.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-082549.png) + image-20240712-082549.png
1. プロンプト上部のタブを2番目のタブ（Okta → `{APP}`）で選択します。
- ![image-20240712-083618.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-083618.png) + image-20240712-083618.png
2. 下部に新たに生成したCustom AttributeとIdP内適切なAttributeをマッピングしてSave Mappingsボタンをクリックして設定を保存します。
- ![image-20240712-085207.png](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240712-085207.png) + image-20240712-085207.png
5. 以降ユーザーをアプリに割り当てます。 @@ -187,7 +187,7 @@ ______ 1. SCIMアプリに戻ってAssignmentsタブで`Assign`ボタンのオプションを通じてユーザーを割り当てます。
- ![Okta Admin Console > Applications > Applications > Custom SCIM App > Assignments](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-035937.png) + Okta Admin Console > Applications > Applications > Custom SCIM App > Assignments
Okta Admin Console > Applications > Applications > Custom SCIM App > Assignments
@@ -196,7 +196,7 @@ ______ 2. **Assign to Groups**：ユーザーグループ単位で割り当て 2. QueryPieアプリに戻ってAdministrator > General > User Management > Usersに移動してユーザーが正常プッシュされたかを確認します。
- ![Administrator > General > User Management > Users > List Details](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240723-040531.png) + Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -206,7 +206,7 @@ ______ #### グループProvisioningチェック
-![Okta Admin Console > Applications > Applications > Custom SCIM App > Push Groups](/administrator-manual/general/user-management/provisioning/okta-provisioning-integration-guide/image-20240430-062231.png) +Okta Admin Console > Applications > Applications > Custom SCIM App > Push Groups
Okta Admin Console > Applications > Applications > Custom SCIM App > Push Groups
diff --git a/src/content/ja/administrator-manual/general/user-management/roles.mdx b/src/content/ja/administrator-manual/general/user-management/roles.mdx index 4f5e0cdb..22896216 100644 --- a/src/content/ja/administrator-manual/general/user-management/roles.mdx +++ b/src/content/ja/administrator-manual/general/user-management/roles.mdx @@ -34,7 +34,7 @@ Rolesページで現在登録された管理者役割を照会できます。 * QueryPieで基本提供する管理者役割はCreated by値がSystemで表記されています。
-![Administrator > General > User Management > Roles](/administrator-manual/general/user-management/roles/screenshot-20240726-130853.png) +Administrator > General > User Management > Roles
Administrator > General > User Management > Roles
@@ -50,7 +50,7 @@ Owner役割はQueryPieシステムに対する全体アクセスが可能な管 Rolesリストで詳細内容を照会しようとする役割をクリックすると詳細ページに進入します。
-![Administrator > General > User Management > Roles > List Details](/administrator-manual/general/user-management/roles/screenshot-20240726-131148.png) +Administrator > General > User Management > Roles > List Details
Administrator > General > User Management > Roles > List Details
@@ -65,7 +65,7 @@ Detailタブには現在照会中の管理者役割に割り当てられたポ 2. モーダルには現在該当役割に割り当てられていないポリシーのリストが表示されます。希望するポリシーをクリックして追加した後、`Assign`ボタンをクリックして保存します。
-![screenshot-20240726-131834.png](/administrator-manual/general/user-management/roles/screenshot-20240726-131834.png) +screenshot-20240726-131834.png
1. 管理者役割詳細ページで追加で割り当てられたポリシーリストを確認できます。 @@ -78,7 +78,7 @@ Detailタブのポリシーリストで除去しようとするポリシーを 確認モーダルで`OK`ボタンを押してポリシー除去を完了します。
-![Administrator > General > User Management > Roles > List Details](/administrator-manual/general/user-management/roles/screenshot-20240726-132233.png) +Administrator > General > User Management > Roles > List Details
Administrator > General > User Management > Roles > List Details
@@ -90,7 +90,7 @@ Administrator > General > User Management > Roles > List Details Rolesリストで、修正しようとする管理者役割詳細ページに進入します。`Edit`ボタンをクリックして修正モーダルを開いた後、名前および説明を修正できます。
-![役割修正モーダル](/administrator-manual/general/user-management/roles/screenshot-20240726-132439.png) +役割修正モーダル
役割修正モーダル
@@ -105,7 +105,7 @@ Rolesリストで、修正しようとする管理者役割詳細ページに進 管理者役割が削除されると既存に該当役割を割り当て受けたユーザーからも即座に該当役割が回収されます。 管理者役割削除はキャンセルが不可能なので慎重に実行してください。
-![screenshot-20240726-132448.png](/administrator-manual/general/user-management/roles/screenshot-20240726-132448.png) +screenshot-20240726-132448.png
@@ -115,7 +115,7 @@ Rolesリストで削除しようとする役割をチェックボックスで選 確認モーダルで削除確認文句「DELETE」を正しく入力して`Delete`ボタンをクリックすると管理者役割削除が完了します。
-![Administrator > General > User Management > Roles](/administrator-manual/general/user-management/roles/screenshot-20240726-132801.png) +Administrator > General > User Management > Roles
Administrator > General > User Management > Roles
@@ -126,7 +126,7 @@ Administrator > General > User Management > Roles Rolesリストで、削除しようとする管理者役割詳細ページに進入します。`Delete`ボタンをクリックして削除確認モーダルを開いた後、削除確認文句「DELETE」を正しく入力して`Delete`ボタンをクリックすると管理者役割削除が完了します。
-![Administrator > General > User Management > Roles > List Details](/administrator-manual/general/user-management/roles/screenshot-20240726-133911.png) +Administrator > General > User Management > Roles > List Details
Administrator > General > User Management > Roles > List Details
diff --git a/src/content/ja/administrator-manual/general/user-management/users.mdx b/src/content/ja/administrator-manual/general/user-management/users.mdx index 7b516674..e5c09313 100644 --- a/src/content/ja/administrator-manual/general/user-management/users.mdx +++ b/src/content/ja/administrator-manual/general/user-management/users.mdx @@ -16,7 +16,7 @@ Userページでは、現在QueryPieに登録されたユーザーリストを Userページでユーザーリストを照会でき、検索およびフィルターを提供します。
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/image-20240714-053822.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -42,7 +42,7 @@ Usersリストで確認可能な情報は以下の通りです。 * Account Locked：多数のログイン失敗によるアカウントロック
-![Descriptionタイプ別表示](/administrator-manual/general/user-management/users/account-status-descriptions.png) +Descriptionタイプ別表示
Descriptionタイプ別表示
@@ -57,7 +57,7 @@ Descriptionタイプ別表示 ユーザーを追加した後、グループおよびポリシーに割り当てて権限を付与できます。
-![Administrator > General > User Management > Users > Add User](/administrator-manual/general/user-management/users/screenshot-20240726-093805.png) +Administrator > General > User Management > Users > Add User
Administrator > General > User Management > Users > Add User
@@ -89,7 +89,7 @@ Admin Roleを付与できる管理者はOwner役割のユーザーのみ可能 事前定義された管理者役割（Admin Role）をユーザーに付与または回収できます。
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/screenshot-20240726-100838.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -116,7 +116,7 @@ Usersページでユーザーをクリックすると詳細情報ページに進 各項目別説明は[ユーザープロファイル文書](users/user-profile)を参照してください。
-![Administrator > General > User Management > Users > List Details](/administrator-manual/general/user-management/users/screenshot-20240726-093748.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -138,7 +138,7 @@ QueryPieを通じて登録したユーザーのみProfile情報修正および 理由入力モーダルが出力されると変更理由を入力後`OK`ボタンをクリックして変更を完了します。
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/screenshot-20240726-104245.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -151,7 +151,7 @@ Administrator > General > User Management > Users 理由入力後`OK`ボタンをクリックするとユーザー無効化が完了します。
-![Administrator > General > User Management > Users > List Details ](/administrator-manual/general/user-management/users/screenshot-20240726-104608.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -174,7 +174,7 @@ Administrator > General > User Management > Users > List Details 理由入力モーダルが出力されると変更理由を入力後`OK`ボタンをクリックして変更を完了します。
-![Administrator > General > User Management > Users](/administrator-manual/general/user-management/users/screenshot-20240726-103711.png) +Administrator > General > User Management > Users
Administrator > General > User Management > Users
@@ -186,7 +186,7 @@ Administrator > General > User Management > Users 理由入力モーダルが出力されると変更理由を入力後`OK`ボタンをクリックして変更を完了します。
-![Administrator > General > User Management > Users > List Details ](/administrator-manual/general/user-management/users/screenshot-20240726-103241.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
@@ -205,7 +205,7 @@ SCIMを通じて連動してきたユーザー情報修正は台帳データ更 入力完了後`Save`ボタンを押して修正を完了します。
-![Administrator > General > User Management > Users > List Details > Edit](/administrator-manual/general/user-management/users/screenshot-20240726-094436.png) +Administrator > General > User Management > Users > List Details > Edit
Administrator > General > User Management > Users > List Details > Edit
@@ -224,7 +224,7 @@ SCIMを通じて連動してきたユーザー削除は台帳データ更新後 確認文句で「DELETE」を入力した後`Delete`ボタンを押すと削除が完了します。
-![Administrator > General > User Management > Users > List Details > Delete User](/administrator-manual/general/user-management/users/screenshot-20240726-101758.png) +Administrator > General > User Management > Users > List Details > Delete User
Administrator > General > User Management > Users > List Details > Delete User
@@ -244,7 +244,7 @@ SCIMを通じて連動してきたユーザーの認証手段はSCIMで管理し #### 一時パスワード発行
-![Administrator > General > User Management > Users > List Details > Authentication](/administrator-manual/general/user-management/users/image-20241218-194814.png) +Administrator > General > User Management > Users > List Details > Authentication
Administrator > General > User Management > Users > List Details > Authentication
@@ -260,7 +260,7 @@ QueryPie 10.2.2からEmail連動設定がされている場合、管理者が一 2. 出力されるポップアップウィンドウの「Password change method」で「User changes own password (via email)」を選択して`Confirm`ボタンを押すとパスワード初期化メールが該当ユーザーのemailアドレスに発送されます。
-![Emailを通じてユーザーが自分のパスワードを直接初期化するよう選択](/administrator-manual/general/user-management/users/image-20241218-195131.png) +Emailを通じてユーザーが自分のパスワードを直接初期化するよう選択
Emailを通じてユーザーが自分のパスワードを直接初期化するよう選択
@@ -271,7 +271,7 @@ Emailを通じてユーザーが自分のパスワードを直接初期化する もし30分を超えてユーザーがこのリンクで接続しない場合、このリンクでパスワードを初期化できませんので、管理者が再び上記手順（User changes own password (via email)）を実行してパスワード初期化メールを発送してあげる必要があります。
-![パスワード初期化メール](/administrator-manual/general/user-management/users/image-20241218-224655.png) +パスワード初期化メール
パスワード初期化メール
@@ -287,7 +287,7 @@ Emailを通じてユーザーが自分のパスワードを直接初期化する
-![パスワード再設定画面](/administrator-manual/general/user-management/users/image-20241220-014612.png) +パスワード再設定画面
パスワード再設定画面
@@ -307,7 +307,7 @@ OTPを再び設定する方法は[My Dashboard](../../../user-manual/my-dashboar 警告モーダルが出力されると`Reset`ボタンをクリックして変更を再設定完了します。
-![Administrator > General > User Management > Users > List Details](/administrator-manual/general/user-management/users/image-20250116-131037.png) +Administrator > General > User Management > Users > List Details
Administrator > General > User Management > Users > List Details
diff --git a/src/content/ja/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx b/src/content/ja/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx index 0ce0b0ad..61bbb7de 100644 --- a/src/content/ja/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx +++ b/src/content/ja/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account.mdx @@ -22,21 +22,21 @@ import { Callout } from 'nextra/components' 1. Admin > General > User Management > Usersメニューに接続します。
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.12.08-PM.png) + <br/>

2. qp-adminアカウントを選択します。
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.14.25-PM.png) + <br/>

3. `Delete`ボタンをクリックします。
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.16.29-PM.png) + <br/>

@@ -59,7 +59,7 @@ import { Callout } from 'nextra/components' 1. qp-adminアカウントログイン時パスワード期限切れ案内画面が露出されます。
- ![
](/administrator-manual/general/user-management/users/password-change-enforcement-and-account-deletion-feature-for-qp-admin-default-account/Screenshot-2025-04-09-at-7.18.40-PM.png) + <br/>

diff --git a/src/content/ja/administrator-manual/general/user-management/users/user-profile.mdx b/src/content/ja/administrator-manual/general/user-management/users/user-profile.mdx index d2d46b30..2c0d983e 100644 --- a/src/content/ja/administrator-manual/general/user-management/users/user-profile.mdx +++ b/src/content/ja/administrator-manual/general/user-management/users/user-profile.mdx @@ -18,7 +18,7 @@ import { Callout } from 'nextra/components' 各Attribute別説明はこのページ下部の**参照：ユーザーAttributeリスト**項目を参照してください。
-![Administrator > General > User Management > Users > List Details > Profileタブ](/administrator-manual/general/user-management/users/user-profile/image-20240526-063720.png) +Administrator > General > User Management > Users > List Details > Profileタブ
Administrator > General > User Management > Users > List Details > Profileタブ
@@ -27,7 +27,7 @@ Administrator > General > User Management > Users > List Details > ### Groups
-![Administrator > General > User Management > Users > List Details > Groupsタブ](/administrator-manual/general/user-management/users/user-profile/image-20240514-162350.png) +Administrator > General > User Management > Users > List Details > Groupsタブ
Administrator > General > User Management > Users > List Details > Groupsタブ
@@ -42,7 +42,7 @@ Administrator > General > User Management > Users > List Details > ### Admin Roles
-![Administrator > General > User Management > Users > List Details > Admin Rolesタブ](/administrator-manual/general/user-management/users/user-profile/image-20240514-162730.png) +Administrator > General > User Management > Users > List Details > Admin Rolesタブ
Administrator > General > User Management > Users > List Details > Admin Rolesタブ
@@ -61,7 +61,7 @@ Administrator > General > User Management > Users > List Details > Administrator > General > Company Management > Allowed Zonesメニューで生成されたAllowed Zoneをユーザーに直接割り当てるか、'IP Registration Request'ワークフローを通じて承認されたStatic IPが自動的に適用された履歴を確認できます。
-![Allowed Zonesタブ](/administrator-manual/general/user-management/users/user-profile/image-20240526-064635.png) +Allowed Zonesタブ
Allowed Zonesタブ
@@ -79,7 +79,7 @@ Allowed Zonesタブ このように`Static IP`属性に登録されたアドレスはこの`Allowed Zone`タブに`Name`が`Static IP`である項目として自動反映され、ユーザーは該当IPからのアクセス権限を付与受けることになります。
-![Screenshot-2025-06-26-at-6.12.22-PM.png](/administrator-manual/general/user-management/users/user-profile/Screenshot-2025-06-26-at-6.12.22-PM.png) +Screenshot-2025-06-26-at-6.12.22-PM.png
#### ワークフローを通じて登録されたStatic IP削除 @@ -101,7 +101,7 @@ Allowed Zonesタブ右側`Attach Allowed Zones`ボタンをクリックすると 割り当てようとするAllowed Zoneを選択して`Attach`ボタンをクリックして割り当てを完了します。
-![Attach Allowed Zoneモーダル](/administrator-manual/general/user-management/users/user-profile/screenshot-20240730-214403.png) +Attach Allowed Zoneモーダル
Attach Allowed Zoneモーダル
@@ -113,7 +113,7 @@ Allowed Zoneタブ下部リストで割り当てを解除しようとする項 ボタンをクリックし、確認モーダルで`Detach`ボタンをクリックして割り当て解除を完了します。
-![Allowed Zones割り当て解除](/administrator-manual/general/user-management/users/user-profile/screenshot-20240730-214952.png) +Allowed Zones割り当て解除
Allowed Zones割り当て解除
diff --git a/src/content/ja/administrator-manual/general/workflow-management/all-requests.mdx b/src/content/ja/administrator-manual/general/workflow-management/all-requests.mdx index c8170540..359db950 100644 --- a/src/content/ja/administrator-manual/general/workflow-management/all-requests.mdx +++ b/src/content/ja/administrator-manual/general/workflow-management/all-requests.mdx @@ -16,7 +16,7 @@ All Requestsでは、QueryPie内のすべての要求履歴を照会し、詳細 Administrator > General > Workflow Management > All Requestsページで要求リストを照会します。
-![Administrator > General > Workflow Management > All Requests](/administrator-manual/general/workflow-management/all-requests/image-20240714-054431.png) +Administrator > General > Workflow Management > All Requests
Administrator > General > Workflow Management > All Requests
@@ -45,7 +45,7 @@ Administrator > General > Workflow Management > All Requests ボックス上にマウスをホバーすると詳細内容を確認できます。
-![Administrator > General > Workflow Management > All Requests > List Detail > Current Status](/administrator-manual/general/workflow-management/all-requests/screenshot-20240725-181602.png) +Administrator > General > Workflow Management > All Requests > List Detail > Current Status
Administrator > General > Workflow Management > All Requests > List Detail > Current Status
diff --git a/src/content/ja/administrator-manual/general/workflow-management/approval-rules.mdx b/src/content/ja/administrator-manual/general/workflow-management/approval-rules.mdx index b7d4a112..c9a5ef51 100644 --- a/src/content/ja/administrator-manual/general/workflow-management/approval-rules.mdx +++ b/src/content/ja/administrator-manual/general/workflow-management/approval-rules.mdx @@ -27,7 +27,7 @@ Approval Rulesページで提供する機能は以下の通りです。 Administrator > General > Workflow Management > Approval Rulesメニューで決裁規則リストを照会できます。
-![Administrator > General > Workflow Management > Approval Rules](/administrator-manual/general/workflow-management/approval-rules/screenshot-20240723-163151.png) +Administrator > General > Workflow Management > Approval Rules
Administrator > General > Workflow Management > Approval Rules
@@ -39,7 +39,7 @@ Administrator > General > Workflow Management > Approval Rules Approval Rulesページ右上の`Add Approval Rule`ボタンをクリックするとモーダルが露出されます。
-![Administrator > General > Workflow Management > Approval Rules > Add Approval Rule](/administrator-manual/general/workflow-management/approval-rules/Screenshot-2025-08-26-at-4.42.57-PM.png) +Administrator > General > Workflow Management > Approval Rules > Add Approval Rule
Administrator > General > Workflow Management > Approval Rules > Add Approval Rule
@@ -118,7 +118,7 @@ Administrator > General > Workflow Management > Approval Rules > Add Administrator > General > Workflow Management > Approval Rules内決裁規則リスト中詳細内容を確認および修正しようとするアイテムをクリックして、モーダルを開きます。
-![Administrator > General > Workflow Management > Approval Rules > Update Approval Rule](/administrator-manual/general/workflow-management/approval-rules/image-20250512-121540.png) +Administrator > General > Workflow Management > Approval Rules > Update Approval Rule
Administrator > General > Workflow Management > Approval Rules > Update Approval Rule
@@ -133,7 +133,7 @@ Administrator > General > Workflow Management > Approval Rules > Upd Administrator > General > Workflow Management > Approval Rules目録で決裁規則を削除できます。
-![Administrator > General > Workflow Management > Approval Rules (削除有効化)](/administrator-manual/general/workflow-management/approval-rules/screenshot-20240725-165423.png) +Administrator > General > Workflow Management > Approval Rules (削除有効化)
Administrator > General > Workflow Management > Approval Rules (削除有効化)
diff --git a/src/content/ja/administrator-manual/general/workflow-management/workflow-configurations.mdx b/src/content/ja/administrator-manual/general/workflow-management/workflow-configurations.mdx index 1d486dcc..3e113359 100644 --- a/src/content/ja/administrator-manual/general/workflow-management/workflow-configurations.mdx +++ b/src/content/ja/administrator-manual/general/workflow-management/workflow-configurations.mdx @@ -21,7 +21,7 @@ Workflow Configurationsでは、以下のような決裁上申および承認関 Approval Rulesページ右上で`⚙️`ボタンをクリックするとWorkflow Configurationsモーダルがポップアップされます。
-![Administrator > General > Workflow Management > Approval Rules > Workflow Configurations](/administrator-manual/general/workflow-management/workflow-configurations/screenshot-20250310-110949.png) +Administrator > General > Workflow Management > Approval Rules > Workflow Configurations
Administrator > General > Workflow Management > Approval Rules > Workflow Configurations
@@ -63,7 +63,7 @@ Tag Display and Filtering in DAC Workflow Requestsトグルスイッチで有効 * DB Access Request：DB Connectionに付与されたタグを目録で見ることができ、フィルターを通じて特定タグがあるコネクションのみフィルタリングできます。
- ![DB Access Reqeust様式でタグ表示およびフィルタリング](/administrator-manual/general/workflow-management/workflow-configurations/image-20250629-180040.png) + DB Access Reqeust様式でタグ表示およびフィルタリング
DB Access Reqeust様式でタグ表示およびフィルタリング
diff --git a/src/content/ja/administrator-manual/kubernetes.mdx b/src/content/ja/administrator-manual/kubernetes.mdx index cc960373..31a41e52 100644 --- a/src/content/ja/administrator-manual/kubernetes.mdx +++ b/src/content/ja/administrator-manual/kubernetes.mdx @@ -7,7 +7,7 @@ import { Callout } from 'nextra/components' # Kubernetes
-![image-20240510-011958.png](/administrator-manual/kubernetes/image-20240510-011958.png) +image-20240510-011958.png
### Overview diff --git a/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers.mdx b/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers.mdx index 8711b949..2c9e8019 100644 --- a/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers.mdx +++ b/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers.mdx @@ -12,7 +12,7 @@ Kubernetes同期用Cloud Providerの照会、作成、修正、削除をサポ Cloud Providerを通じて、クラウドプラットフォーム内のKubernetesリソースを同期し、QueryPieで管理するクラスターに一括登録することが可能です。
-![Administrator > Kubernetes > Connection Management > Cloud Providers](/administrator-manual/kubernetes/connection-management/cloud-providers/image-20240721-053703.png) +Administrator > Kubernetes > Connection Management > Cloud Providers
Administrator > Kubernetes > Connection Management > Cloud Providers
@@ -45,7 +45,7 @@ Administrator > Kubernetes > Connection Management > Cloud Providers ### Cloud Provider削除
-![image-20240721-053752.png](/administrator-manual/kubernetes/connection-management/cloud-providers/image-20240721-053752.png) +image-20240721-053752.png
1. Administrator > Kubernetes > Connection Management > Cloud Providersメニューに移動します。 diff --git a/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx b/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx index 8e24a412..14227414 100644 --- a/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx +++ b/src/content/ja/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws.mdx @@ -33,7 +33,7 @@ QueryPieは、AWS EKS Kubernetesクラスター接続のために、同期時に したがって、クラスター認証モードがConfigMapでのみ設定されている場合、接続が困難な部分があり、円滑な同期のためにAWSコンソールでモード変更を事前に作業しておくことをお勧めします。
-![AWS Console > EKS > Clusters > `{cluster}` > Access > Access configuration > Manage access](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240512-134234.png) +AWS Console > EKS > Clusters > `{cluster}` > Access > Access configuration > Manage access
AWS Console > EKS > Clusters > `{cluster}` > Access > Access configuration > Manage access
@@ -42,7 +42,7 @@ AWS Console > EKS > Clusters > `{cluster}` > Access > Access conf 1. AWS ConsoleにEKS管理者権限を持つアカウントでアクセスします。 2. **Elastic Kubernetes Service (EKS)** メニューに移動します。 3. 対象EKSクラスターが位置するリージョン(Region)に移動します。 - * 例) ![image-20240512-134604.png](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240512-134604.png) + * 예) image-20240512-134604.png 4. 対象EKSクラスターを選択して詳細ページに移動します。 5. AccessタブをクリックしてAccess configuration現況を確認します。 6. Authentication modeが **"ConfigMap"** であれば、右側の **Manage access** ボタンをクリックします。 @@ -53,7 +53,7 @@ AWS Console > EKS > Clusters > `{cluster}` > Access > Access conf ### QueryPieでAWS連携情報登録
-![Administrator > Kubernetes > Connection Management > Cloud Providers > Create Provider](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240721-054036.png) +Administrator > Kubernetes > Connection Management > Cloud Providers > Create Provider
Administrator > Kubernetes > Connection Management > Cloud Providers > Create Provider
@@ -66,7 +66,7 @@ Administrator > Kubernetes > Connection Management > Cloud Providers &g 5. **Region** 項目で同期したいリソースのリージョンを選択します。 6. リソースを同期するために必要な **Credential** 情報を入力します。
- ![image-20240721-054206.png](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240721-054206.png) + image-20240721-054206.png
1. **Default Credentials** : QueryPieサーバーが同じAWSアカウントにインストールされている場合、QueryPieがインストールされたEC2インスタンスにIAMロールを割り当てて同じAWS内のリソースを同期することができます。 2. **Cross Account Role** : IAMロールを作成して他のAWSアカウントのリソースを同期することができます。画面に表示されたステップに従って同期のための権限を作成し、ポリシーを割り当ててください。 @@ -90,7 +90,7 @@ A. すでに **Credential** が`Default Credentials`でありながら同じ`Re ### 登録されたAWS Cloud Provider同期および管理
-![Administrator > Kubernetes > Connection Management > Cloud Providers > List Details](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240721-054313.png) +Administrator > Kubernetes > Connection Management > Cloud Providers > List Details
Administrator > Kubernetes > Connection Management > Cloud Providers > List Details
@@ -113,13 +113,13 @@ Administrator > Kubernetes > Connection Management > Cloud Providers &g ### Dry Run/Synchronization Log表記文句 -| | **発生時点** | **文句** | -| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | -| ✔️ | Dry RunまたはSynchronize同期開始 | Cluster synchronization started. | -| ✔️ | 新規クラスター追加完了 | New Cluster is added: `{Cluster Name}` (`{API URL}`). | -| ✔️ | 既存クラスター情報更新完了 | Cluster `{Cluster Name}` is updated | -| ✔️ | 既存クラスター削除完了 | Cluster `{Cluster Name}` is removed | -| ✔️ | Dry RunまたはSynchronize同期成功終了 | Cluster synchronization succeeded. | -| ![image-20240822-082024.png](/administrator-manual/kubernetes/connection-management/cloud-providers/synchronizing-kubernetes-resources-from-aws/image-20240822-082024.png) | EKSクラスターの認証モードがEKS APIを許可しない場合同期スキップ. ConfigMapモードでEKS APIを許可するように変更必要. | Skipping sync. Cluster `{Cluster Name}`'s authentication mode blocks EKS access entry API. To manage access, enable EKS API access. | -| ❌ | すでに重複したクラスター名が確認されて同期失敗 | Cluster synchronization failed. The cluster name "`{Cluster Name}`" is already in use by another cluster. To synchronize it, delete the existing cluster. | -| ❌ | Dry RunまたはSynchronize同期失敗終了 | Cluster synchronization failed. + `{additional statement}` | +| | **발생 시점** | **문구** | +| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | +| ✔️ | Dry Run 또는 Synchronize 동기화 시작 | Cluster synchronization started. | +| ✔️ | 신규 클러스터 추가 완료 | New Cluster is added: `{Cluster Name}` (`{API URL}`). | +| ✔️ | 기존 클러스터 정보 업데이트 완료 | Cluster `{Cluster Name}` is updated | +| ✔️ | 기존 클러스터 제거 완료 | Cluster `{Cluster Name}` is removed | +| ✔️ | Dry Run 또는 Synchronize 동기화 성공적으로 종료 | Cluster synchronization succeeded. | +| image-20240822-082024.png | EKS 클러스터의 인증 모드가 EKS API를 허용하지 않는 경우 동기화 스킵. ConfigMap 모드에서 EKS API를 허용하도록 변경 필요. | Skipping sync. Cluster `{Cluster Name}`'s authentication mode blocks EKS access entry API. To manage access, enable EKS API access. | +| ❌ | 이미 중복된 클러스터명이 확인되어 동기화 실패 | Cluster synchronization failed. The cluster name “`{Cluster Name}`” is already in use by another cluster. To synchronize it, delete the existing cluster. | +| ❌ | Dry Run 또는 Synchronize 동기화 실패 종료 | Cluster synchronization failed. + `{additional statement}` | diff --git a/src/content/ja/administrator-manual/kubernetes/connection-management/clusters.mdx b/src/content/ja/administrator-manual/kubernetes/connection-management/clusters.mdx index 0949fdd5..ad31ff45 100644 --- a/src/content/ja/administrator-manual/kubernetes/connection-management/clusters.mdx +++ b/src/content/ja/administrator-manual/kubernetes/connection-management/clusters.mdx @@ -12,7 +12,7 @@ QueryPieでKubernetesクラスター資産の照会、作成、修正、削除 Cloud Providerを通じて同期してきたKubernetesクラスターおよび手動で登録したKubernetesクラスターすべて同じページで管理します。
-![Administrator > Kubernetes > Connection Management > Clusters](/administrator-manual/kubernetes/connection-management/clusters/image-20240721-054705.png) +Administrator > Kubernetes > Connection Management > Clusters
Administrator > Kubernetes > Connection Management > Clusters
@@ -45,7 +45,7 @@ Administrator > Kubernetes > Connection Management > Clusters ### Cluster削除
-![image-20240721-054752.png](/administrator-manual/kubernetes/connection-management/clusters/image-20240721-054752.png) +image-20240721-054752.png
1. Administrator > Kubernetes > Connection Management > Clustersメニューに移動します。 diff --git a/src/content/ja/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx b/src/content/ja/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx index f01e07e3..89c22d61 100644 --- a/src/content/ja/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx +++ b/src/content/ja/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters.mdx @@ -14,7 +14,7 @@ QueryPieでは、アクセス制御を適用するオンプレミスなどに位 個別サーバーを手動で登録するためには、サーバーの基本的な情報入力が必要です。
-![image-20240721-054859.png](/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters/image-20240721-054859.png) +image-20240721-054859.png
1. Administrator > Kubernetes > Connection Management > Clustersメニューに移動します。 @@ -63,7 +63,7 @@ QueryPieでは、アクセス制御を適用するオンプレミスなどに位 ### Kubernetesクラスター連携用スクリプト利用案内
-![image-20240511-033842.png](/administrator-manual/kubernetes/connection-management/clusters/manually-registering-kubernetes-clusters/image-20240511-033842.png) +image-20240511-033842.png
* 管理者は事前に該当対象Kubernetesクラスターにアクセスが可能でなければなりません。 diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control.mdx index 750b250a..4647b9bf 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control.mdx @@ -12,7 +12,7 @@ QueryPieユーザーおよびグループに組織で管理するKubernetesク Access ControlはKubernetesアクセス権限を実装および適用するための最終段階を意味します。
-![Administrator > Kubernetes > K8s Access Control > Access Control](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065226.png) +Administrator > Kubernetes > K8s Access Control > Access Control
Administrator > Kubernetes > K8s Access Control > Access Control
@@ -22,7 +22,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control ### Access Control現況照会
-![Administrator > Kubernetes > K8s Access Control > Access Control > List Details](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065443.png) +Administrator > Kubernetes > K8s Access Control > Access Control > List Details
Administrator > Kubernetes > K8s Access Control > Access Control > List Details
@@ -40,7 +40,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 5. Access Controlリストで行をクリックすると、対象ユーザー/グループに対する詳細ページに移動します。 1. **Roles**
- ![image-20240721-065530.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065530.png) + image-20240721-065530.png
1. デフォルトで指定されるタブで付与されたRoleリストを照会できます。 2. Role名で検索可能です。 @@ -53,7 +53,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 6. **Granted By** : 該当Roleをユーザー/グループに付与した管理者名 4. 各Role行をクリックすると該当Roleの詳細情報をドロワー形態で提供します。
- ![image-20240721-065559.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065559.png) + image-20240721-065559.png
1. 上段には基本情報が以下のように露出されます： 1. **Name** : Role名 @@ -67,7 +67,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 1. **Name** : Policy名 * (ポリシー情報を照会できるリンクを提供します。)
- ![image-20240721-065637.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065637.png) + image-20240721-065637.png
2. **Description** : Policy詳細説明 3. **Version** : Policy版 @@ -75,7 +75,7 @@ Administrator > Kubernetes > K8s Access Control > Access Control > L 5. **Assigned By** : 該当ポリシーを割り当てた管理者名 2. **Clusters**
- ![image-20240721-065710.png](/administrator-manual/kubernetes/k8s-access-control/access-control/image-20240721-065710.png) + image-20240721-065710.png
1. 付与されたRoleによってアクセス可能なKubernetesクラスターリストを列挙します。 2. Cluster名、Role名で検索可能です。 diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx index c0a4cd4e..683413a7 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles.mdx @@ -13,7 +13,7 @@ import { Callout } from 'nextra/components' ### Kubernetes役割付与
-![Administrator > Kubernetes > K8s Access Control > Access Control](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-065226.png) +Administrator > Kubernetes > K8s Access Control > Access Control
Administrator > Kubernetes > K8s Access Control > Access Control
@@ -22,14 +22,14 @@ Administrator > Kubernetes > K8s Access Control > Access Control 1. Administrator > Kubernetes > K8s Access Control > Access Controlメニューに移動します。 2. 権限を付与するユーザーまたはユーザーグループを選択して詳細ページに移動します。
- ![Administrator > Kubernetes > K8s Access Control > Access Control > List Details](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-065443.png) + Administrator > Kubernetes > K8s Access Control > Access Control > List Details
Administrator > Kubernetes > K8s Access Control > Access Control > List Details
3. Rolesタブ右側の`+ Grant Roles`ボタンをクリックして付与するRole左側チェックボックスをチェックし、満了日を指定します。
- ![image-20240721-070449.png](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-070449.png) + image-20240721-070449.png
1. Role名で検索可能です。 2. 既存にすでに割り当てられている役割はチェックボックスが非活性化されます。 @@ -46,14 +46,14 @@ Administrator > Kubernetes > K8s Access Control > Access Control ### Kubernetes役割回収
-![image-20240721-070526.png](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-070526.png) +image-20240721-070526.png
1. Administrator > Kubernetes > K8s Access Control > Access Controlメニューに移動します。 2. 権限を回収するユーザーまたはユーザーグループを選択して詳細ページに移動します。 3. Rolesタブで全体選択または個別選択ボックスにチェックするとカラムバーに露出された`Revoke`ボタンをクリックします。
- ![image-20240721-070637.png](/administrator-manual/kubernetes/k8s-access-control/access-control/granting-and-revoking-kubernetes-roles/image-20240721-070637.png) + image-20240721-070637.png
4. 確認ウィンドウで`Revoke`ボタンクリック時、選択した役割権限がユーザー/グループから回収されてリストから消えます。 5. (`Cancel`ボタンクリック時は確認ウィンドウのみ閉じます。) diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies.mdx index be40f09c..06cb4a60 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies.mdx @@ -12,7 +12,7 @@ import { Callout } from 'nextra/components' PolicyはKubernetesアクセス権限を実装および適用するための最も最初の段階です。
-![Administrator > Kubernetes > K8s Access Control > Policies](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072128.png) +Administrator > Kubernetes > K8s Access Control > Policies
Administrator > Kubernetes > K8s Access Control > Policies
@@ -22,7 +22,7 @@ Administrator > Kubernetes > K8s Access Control > Policies ### Policy照会
-![Administrator > Kubernetes > K8s Access Control > Policies > List Details](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072306.png) +Administrator > Kubernetes > K8s Access Control > Policies > List Details
Administrator > Kubernetes > K8s Access Control > Policies > List Details
@@ -40,13 +40,13 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 5. 各行をクリックするとポリシー詳細情報照会が可能です。 1. **Detail**
- ![image-20240721-072345.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072345.png) + image-20240721-072345.png
1. デフォルトで指定されるタブでポリシーで定義されたコードを照会できます。 2. Detailタブに位置する時、右側に`Go to Editor Mode`ボタンがあり、これをクリックすると該当Code Editorページ画面に切り替わります。 2. **Roles**
- ![image-20240721-072412.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072412.png) + image-20240721-072412.png
1. 該当ポリシーが割り当てられているRoleリストを列挙します。 2. リストは各Roleごとに以下の情報を露出します： @@ -56,7 +56,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 4. **Assigned By** : 該当ポリシーをRoleに割り当てた管理者名 3. 各行をクリックするとRoleに対する詳細情報をドロワー形態で提供します。
- ![image-20240721-072435.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072435.png) + image-20240721-072435.png
1. **Name** : Role名 * 該当ロール詳細ページリンクを提供します。 @@ -68,7 +68,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 7. **Updated By** : 最終Role修正者名 3. **Versions**
- ![image-20240721-072503.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072503.png) + image-20240721-072503.png
1. 該当ポリシーの各版に対する履歴を列挙します。 * ポリシー版はCodeが修正されて保存されるとアップデートされます。 @@ -79,7 +79,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 4. **Updated By** : 該当版修正者名 3. 各行をクリックすると版に対する詳細情報をドロワー形態で提供します。
- ![image-20240721-072547.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072547.png) + image-20240721-072547.png
1. **(Title)** : ポリシー名 2. **Version** : ポリシー版 @@ -92,7 +92,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Policy作成
-![image-20240721-072621.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072621.png) +image-20240721-072621.png
1. Administrator > Kubernetes > K8s Access Control > Policiesメニューに移動します。 @@ -108,7 +108,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Policy修正
-![image-20240721-072705.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072705.png) +image-20240721-072705.png
1. Administrator > Kubernetes > K8s Access Control > Policiesメニューに移動します。 @@ -122,7 +122,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Policy複製
-![image-20240721-072804.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072804.png) +image-20240721-072804.png
1. Administrator > Kubernetes > K8s Access Control > Policiesメニューに移動します。 @@ -137,7 +137,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De ### Policy削除
-![image-20240721-072845.png](/administrator-manual/kubernetes/k8s-access-control/policies/image-20240721-072845.png) +image-20240721-072845.png
1. Administrator > Kubernetes > K8s Access Control > Policiesメニューに移動します。 diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx index e3e92f3d..81cadc1c 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide.mdx @@ -22,7 +22,7 @@ QueryPie KACではYaml形態のPolicyを通じてk8sに対するアクセス制 ### Resources関連設定ガイド
-![3rd Party Client Tool - Lens画面](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-action-configuration-reference-guide/screenshot-lens-resources-events.png) +3rd Party Client Tool - Lens画面
3rd Party Client Tool - Lens画面
diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx index d5157f91..3e6e4cc8 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide.mdx @@ -17,7 +17,7 @@ KubernetesポリシーはPolicy as a Code(PaC)で運営され、YAML形態をベ モーダルはコード編集を助ける役割で、全体モーダルによって挿入された内容はコードエディター上で削除が可能です。
-![Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073114.png) +Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
@@ -25,14 +25,14 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 1. **Add Resources** モーダル
- ![image-20240721-073346.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073346.png) + image-20240721-073346.png
1. Spec: Allow、Spec: Deny二箇所で同じように動作します。 2. Cluster名でリソース検索が可能です。 3. チェックボックスにチェックしたリソースを`Add`ボタンをクリックしてコードに挿入します。 2. **Set Subjects** モーダル
- ![image-20240721-073434.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073434.png) + image-20240721-073434.png
1. Spec: Allowでのみ動作します。 2. **Kubernetes Groups** : (Required) 該当フィールドを通じてKubePie ProxyがAPI呼び出し実行のためにimpersonateするKubernetesグループを指定します。 @@ -43,7 +43,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 4. エディターにある内容を基にモーダルが既存の情報を一緒に表記し、`Set`ボタンを押すと変更事項をエディターで上書きします。 3. **Add Actions** モーダル
- ![image-20240721-073515.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073515.png) + image-20240721-073515.png
1. Spec: Allow、Spec: Deny二箇所で同じように動作します。 2. **API Groups** : デフォルトで"*"が提供され、管理者が修正可能で、「,」区切りで複数入力可能です。 @@ -68,7 +68,7 @@ Administrator > Kubernetes > K8s Access Control > Policies > List De 8. コード上でappendに該当する部分で既存の追加されたアクションを初期化せずに新しく追加が可能です。 4. **Set Conditions** モーダル
- ![image-20240721-073628.png](/administrator-manual/kubernetes/k8s-access-control/policies/kubernetes-policy-ui-code-helper-guide/image-20240721-073628.png) + image-20240721-073628.png
1. 該当項目はすべて選択事項です。 2. エディターにある内容を基にモーダルが既存の情報を一緒に表記し、`Set`ボタンを押すと変更事項をエディターで上書きします。 diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx index a3177120..496fdb78 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies.mdx @@ -14,7 +14,7 @@ KubernetesポリシーはPolicy as a Code(PaC)で運営され、YAML形態をベ ### Policyコード編集
-![Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode](/administrator-manual/kubernetes/k8s-access-control/policies/setting-kubernetes-policies/image-20240721-073114.png) +Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
Administrator > Kubernetes > K8s Access Control > Policies > List Details > Go to Editor Mode
diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles.mdx index 8ed4dbbb..bff196b1 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles.mdx @@ -12,7 +12,7 @@ import { Callout } from 'nextra/components' RoleはKubernetesアクセス権限を実装および適用するためのPolicy以降の段階として、Policyの集合であり、ユーザー/グループとポリシーの連携を担う権限を意味します。
-![Administrator > Kubernetes > K8s Access Control > Roles](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-070743.png) +Administrator > Kubernetes > K8s Access Control > Roles
Administrator > Kubernetes > K8s Access Control > Roles
@@ -22,7 +22,7 @@ Administrator > Kubernetes > K8s Access Control > Roles ### Roleを照会する
-![Administrator > Kubernetes > K8s Access Control > Roles > List Details](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-070912.png) +Administrator > Kubernetes > K8s Access Control > Roles > List Details
Administrator > Kubernetes > K8s Access Control > Roles > List Details
@@ -41,7 +41,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 5. 各行をクリックすると役割詳細情報照会が可能です。 1. **Policies**
- ![image-20240721-070945.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-070945.png) + image-20240721-070945.png
1. デフォルトで指定されるタブで割り当てられたポリシーリストを照会できます。 2. テーブルリストには各ポリシー別に以下の情報を露出します： @@ -52,7 +52,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 5. **Assigned By** : 該当ポリシーを割り当てた管理者名 3. 各ポリシー行をクリックすると該当ポリシーの詳細情報をドロワー形態で提供します。
- ![image-20240721-071031.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071031.png) + image-20240721-071031.png
1. 上段には基本情報が以下のように露出されます： 1. **Name** : Policy名 @@ -64,7 +64,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 2. 下段にはポリシーがコードで露出されます。 2. **Users/Groups**
- ![image-20240721-071134.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071134.png) + image-20240721-071134.png
1. 該当Roleが付与されているユーザー/グループリストを列挙します。 2. ユーザー/グループ名で検索可能です。 @@ -76,7 +76,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 5. **Granted At** : ユーザー/グループに該当Roleが付与された日時 3. **Clusters**
- ![image-20240721-071233.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071233.png) + image-20240721-071233.png
1. 該当Roleによってアクセス可能なKubernetesクラスターリストを列挙します。 2. Cluster名で検索可能です。 @@ -93,7 +93,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Roleを作成する
-![image-20240721-071306.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071306.png) +image-20240721-071306.png
1. Administrator > Kubernetes > K8s Access Control > Rolesメニューに移動します。 @@ -109,7 +109,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Roleを修正する
-![image-20240721-071337.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071337.png) +image-20240721-071337.png
1. Administrator > Kubernetes > K8s Access Control > Rolesメニューに移動します。 @@ -123,7 +123,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Roleを削除する
-![image-20240721-071429.png](/administrator-manual/kubernetes/k8s-access-control/roles/image-20240721-071429.png) +image-20240721-071429.png
1. Administrator > Kubernetes > K8s Access Control > Rolesメニューに移動します。 diff --git a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx index c45a6fe2..25c70835 100644 --- a/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx +++ b/src/content/ja/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles.mdx @@ -16,7 +16,7 @@ Roleは複数のポリシーを総合して単一役割で定義するのに使 ### Roleポリシーを割り当てる
-![Administrator > Kubernetes > K8s Access Control > Roles > List Details](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071540.png) +Administrator > Kubernetes > K8s Access Control > Roles > List Details
Administrator > Kubernetes > K8s Access Control > Roles > List Details
@@ -27,7 +27,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai 3. Policiesタブ右側の`+ Assign Policies`ボタンをクリックします。 4. 割り当てるポリシーを検討した後、左側のチェックボックスをチェックします。
- ![image-20240721-071758.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071758.png) + image-20240721-071758.png
1. ポリシー名で検索可能です。 2. 既に割り当てられているポリシーはチェックボックスが選択できません。 @@ -35,7 +35,7 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai * **Name** : ポリシー名 * ポリシー情報を照会できるモーダルリンクを提供します。
- ![image-20240721-071822.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071822.png) + image-20240721-071822.png
5. `Assign`ボタンを押すとチェックボックスをチェックした対象ポリシーを割り当てます。 6. (`Cancel`ボタンを押すと該当モーダルを変更事項なしで終了します。) @@ -44,14 +44,14 @@ Administrator > Kubernetes > K8s Access Control > Roles > List Detai ### Roleポリシー割り当て解除
-![image-20240721-071910.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071910.png) +image-20240721-071910.png
1. Administrator > Kubernetes > K8s Access Control > Rolesメニューに移動します。 2. Rolesリストで対象Role行をクリックして詳細ページに移動します。 3. Policiesタブで全体選択または個別選択ボックスにチェックするとカラムバーに表示される`Unassign`ボタンをクリックします。
- ![image-20240721-071940.png](/administrator-manual/kubernetes/k8s-access-control/roles/setting-kubernetes-roles/image-20240721-071940.png) + image-20240721-071940.png
4. 確認ウィンドウで`Unassign`ボタンクリック時、選択したアイテムが割り当て解除されてリストから消えます。 5. (`Cancel`ボタンクリック時は確認ウィンドウのみ閉じます。) diff --git a/src/content/ja/administrator-manual/kubernetes/kac-general-configurations.mdx b/src/content/ja/administrator-manual/kubernetes/kac-general-configurations.mdx index 7c2aab90..1bc422a4 100644 --- a/src/content/ja/administrator-manual/kubernetes/kac-general-configurations.mdx +++ b/src/content/ja/administrator-manual/kubernetes/kac-general-configurations.mdx @@ -17,7 +17,7 @@ import { Callout } from 'nextra/components' Kubernetesクラスターアクセス制御、権限管理、セッションポリシーなどコンテナベース環境でのセキュリティのための設定を提供します。
-![Kubernetes Configurations options](/administrator-manual/kubernetes/kac-general-configurations/image-20251107-090909.png) +Kubernetes Configurations options
Kubernetes Configurations options
diff --git a/src/content/ja/administrator-manual/servers.mdx b/src/content/ja/administrator-manual/servers.mdx index be7c27da..7ea2a5b5 100644 --- a/src/content/ja/administrator-manual/servers.mdx +++ b/src/content/ja/administrator-manual/servers.mdx @@ -7,7 +7,7 @@ import { Callout } from 'nextra/components' # Servers
-![screenshot-20240523-195046.png](/administrator-manual/servers/screenshot-20240523-195046.png) +screenshot-20240523-195046.png
### Overview diff --git a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers.mdx b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers.mdx index 979ea138..4151357d 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers.mdx @@ -12,7 +12,7 @@ QueryPieでは、サーバー登録および管理のためのCloud Providerと Cloud Provider内のリソースを同期し、QueryPieで管理するサーバーに登録し、ユーザーおよびグループに同期してきたサーバーに対するアクセス権限を付与し、ポリシーを設定できます。
-![Administrator > Servers > Connection Management > Cloud Providers](/administrator-manual/servers/connection-management/cloud-providers/image-20240902-044659.png) +Administrator > Servers > Connection Management > Cloud Providers
Administrator > Servers > Connection Management > Cloud Providers
@@ -46,7 +46,7 @@ Administrator > Servers > Connection Management > Cloud Providers ### Cloud Provider削除
-![image-20240902-044732.png](/administrator-manual/servers/connection-management/cloud-providers/image-20240902-044732.png) +image-20240902-044732.png
1. Administrator > Servers > Connection Management > Cloud Providersメニューに移動します。 diff --git a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx index 33d75ea1..80177e0c 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws.mdx @@ -16,7 +16,7 @@ AWS内のリソースを同期し、QueryPieで管理するサーバーに登録 ### QueryPieでAWS連携情報登録
-![Administrator > Servers > Connection Management > Cloud Providers > Create Provider](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20241220-095625.png) +Administrator > Servers > Connection Management > Cloud Providers > Create Provider
Administrator > Servers > Connection Management > Cloud Providers > Create Provider
@@ -53,7 +53,7 @@ A. すでに **Creadential** が`Default Credentials`でありながら同じ`R ### Credentialタイプ別認証方式設定
-![Credentialタイプ](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20240902-044927.png) +Credentialタイプ
Credentialタイプ
@@ -68,7 +68,7 @@ Credentialタイプ **Save Credential for Synchronizationオプション**
-![Save Credential for Synchronization](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20241220-095857.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -83,7 +83,7 @@ Save Credential for Synchronization ### 登録されたAWS Cloud Provider同期および管理
-![Administrator > Servers > Connection Management > Cloud Providers > List Details](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-aws/image-20241220-100236.png) +Administrator > Servers > Connection Management > Cloud Providers > List Details
Administrator > Servers > Connection Management > Cloud Providers > List Details
diff --git a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx index 6df8989e..ad77c3f5 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure.mdx @@ -15,7 +15,7 @@ Azure内のリソースを同期し、QueryPieで管理するサーバーに登 ### QueryPieでAzure連携情報登録
-![Administrator > Servers > Connection Management > Cloud Providers > Create Provider](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure/image-20241220-101742.png) +Administrator > Servers > Connection Management > Cloud Providers > Create Provider
Administrator > Servers > Connection Management > Cloud Providers > Create Provider
@@ -48,7 +48,7 @@ Administrator > Servers > Connection Management > Cloud Providers > **Save Credential for Synchronizationオプション**
-![Save Credential for Synchronization](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure/image-20241220-091144.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -62,7 +62,7 @@ Save Credential for Synchronization ### 登録されたAzure Cloud Provider同期および管理
-![Administrator > Servers > Connection Management > Cloud Providers > List Details](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-azure/image-20241220-104437.png) +Administrator > Servers > Connection Management > Cloud Providers > List Details
Administrator > Servers > Connection Management > Cloud Providers > List Details
diff --git a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx index f15dfe13..8afddc60 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp.mdx @@ -15,7 +15,7 @@ GCP内のリソースを同期し、QueryPieで管理するサーバーに登録 ### QueryPieでGCP連携情報登録
-![Administrator > Servers > Connection Management > Cloud Providers > Create Provider](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp/image-20241220-120114.png) +Administrator > Servers > Connection Management > Cloud Providers > Create Provider
Administrator > Servers > Connection Management > Cloud Providers > Create Provider
@@ -47,7 +47,7 @@ Administrator > Servers > Connection Management > Cloud Providers > **Save Credential for Synchronizationオプション**
-![Save Credential for Synchronization](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp/image-20241220-094727.png) +Save Credential for Synchronization
Save Credential for Synchronization
@@ -61,7 +61,7 @@ Save Credential for Synchronization ### 登録されたGCP Cloud Provider同期および管理
-![Administrator > Servers > Connection Management > Cloud Providers > List Details](/administrator-manual/servers/connection-management/cloud-providers/synchronizing-server-resources-from-gcp/image-20241222-132041.png) +Administrator > Servers > Connection Management > Cloud Providers > List Details
Administrator > Servers > Connection Management > Cloud Providers > List Details
diff --git a/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations.mdx b/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations.mdx index a76e0d48..46954ba4 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations.mdx @@ -15,7 +15,7 @@ ProxyJump設定を通じて、他のNetwork ZoneまたはVPCにインストー ### ProxyJump照会
-![Administrator > Servers > Connection Management > ProxyJump Configurations](/administrator-manual/servers/connection-management/proxyjump-configurations/image-20240829-012626.png) +Administrator > Servers > Connection Management > ProxyJump Configurations
Administrator > Servers > Connection Management > ProxyJump Configurations
@@ -42,7 +42,7 @@ Administrator > Servers > Connection Management > ProxyJump Configurati ### ProxyJump削除
-![image-20240909-083933.png](/administrator-manual/servers/connection-management/proxyjump-configurations/image-20240909-083933.png) +image-20240909-083933.png
1. Administrator > Servers > Connection Management > ProxyJump Configurationsメニューに移動します。 diff --git a/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx b/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx index 85807aa5..7e46e82a 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump.mdx @@ -16,7 +16,7 @@ QueryPieがJump Hostにアクセスが可能でなければなりません。 ### ProxyJump作成
-![Administrator > Servers > Connection Management > ProxyJump Configurations > Create ProxyJump](/administrator-manual/servers/connection-management/proxyjump-configurations/creating-proxyjump/image-20250116-115457.png) +Administrator > Servers > Connection Management > ProxyJump Configurations > Create ProxyJump
Administrator > Servers > Connection Management > ProxyJump Configurations > Create ProxyJump
diff --git a/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx b/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx index cf2af522..ddd87686 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp.mdx @@ -21,7 +21,7 @@ RDP Protocolを通じてリモートアクセスするには、管理しよう
-![Administrator > Servers > Connection Management > Server Agents for RDP](/administrator-manual/servers/connection-management/server-agents-for-rdp/image-20250707-011843.png) +Administrator > Servers > Connection Management > Server Agents for RDP
Administrator > Servers > Connection Management > Server Agents for RDP
@@ -68,7 +68,7 @@ QueryPieに登録されるServer AgentのHost情報はWindows Serverが持って この場合、以下のように解決が可能です。
-![image-20240731-024502.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/image-20240731-024502.png) +image-20240731-024502.png
1. Administrator > Servers > Connection Management > Server Agents for RDPメニューに移動します。 @@ -89,7 +89,7 @@ QueryPieウェブ画面で直接Server Agentを最新版にアップデートで ### Server Agents削除
-![image-20240728-154821.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/image-20240728-154821.png) +image-20240728-154821.png
1. Administrator > Servers > Connection Management > Server Agents for RDPメニューに移動します。 diff --git a/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx b/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx index 1feba731..2aa5058d 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent.mdx @@ -15,7 +15,7 @@ QueryPie Server Agentインストール後、QueryPie内ServersメニューにWi ### Server Agentインストール
-![image-20240728-163032.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent/image-20240728-163032.png) +image-20240728-163032.png
* Server Agentダウンロードページにアクセスします。 @@ -26,7 +26,7 @@ QueryPie Server Agentインストール後、QueryPie内ServersメニューにWi 既存のようにダウンロードリンクのページを使用してダウンロードを受け取ることもできます。 （QueryPie使用者ではない人が外部からエージェントをダウンロードしなければならない場合使用）
-![RDP Server Agentダウンロードボタン提供](/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent/image-20251010-085601.png) +RDP Server Agentダウンロードボタン提供
RDP Server Agentダウンロードボタン提供
@@ -89,7 +89,7 @@ CMDでServer Agentインストールファイル位置に移動後、以下の ### Server Agent削除
-![image-20240829-010643.png](/administrator-manual/servers/connection-management/server-agents-for-rdp/installing-and-removing-server-agent/image-20240829-010643.png) +image-20240829-010643.png
1. Administrator > Servers > Connection Management > Server Agents for RDPページにアクセスします。 diff --git a/src/content/ja/administrator-manual/servers/connection-management/server-groups.mdx b/src/content/ja/administrator-manual/servers/connection-management/server-groups.mdx index 1927f96c..306c038d 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/server-groups.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/server-groups.mdx @@ -10,7 +10,7 @@ QueryPieではServer Group単位でポリシーを設定し、アクセス権限 また、サーバーのTagを通じて一括でサーバーを選択したり、今後同期されるサーバーが自動でサーバーグループに選択されるようにできます。
-![Administrator > Servers > Connection Management > Server Groups](/administrator-manual/servers/connection-management/server-groups/image-20240902-045633.png) +Administrator > Servers > Connection Management > Server Groups
Administrator > Servers > Connection Management > Server Groups
@@ -40,7 +40,7 @@ Administrator > Servers > Connection Management > Server Groups ### Server Group削除
-![image-20240728-151520.png](/administrator-manual/servers/connection-management/server-groups/image-20240728-151520.png) +image-20240728-151520.png
1. Administrator > Servers > Connection Management > Server Groupsメニューに移動します。 diff --git a/src/content/ja/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx b/src/content/ja/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx index 1f417974..14557691 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups.mdx @@ -21,7 +21,7 @@ import { Callout } from 'nextra/components' ### サーバーグループ作成
-![Administrator > Servers > Connection Management > Server Groups > Create Server Group](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20250123-113012.png) +Administrator > Servers > Connection Management > Server Groups > Create Server Group
Administrator > Servers > Connection Management > Server Groups > Create Server Group
@@ -50,7 +50,7 @@ Administrator > Servers > Connection Management > Server Groups > Cr #### 1. 基本情報入力およびサーバーをTagで追加
-![image-20240902-045749.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20240902-045749.png) +image-20240902-045749.png
* Name : サーバーグループの名前を入力します。 @@ -60,7 +60,7 @@ Administrator > Servers > Connection Management > Server Groups > Cr #### 2. Serverを手動で追加
-![image-20241028-003400.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20241028-003400.png) +image-20241028-003400.png
* Serversでは該当サーバーグループに属するサーバーを確認したり、サーバーをサーバーグループに手動追加できます。 @@ -72,7 +72,7 @@ Administrator > Servers > Connection Management > Server Groups > Cr 11.3.0でServer groupに追加するサーバーリストポップアップでタグを使用して対象をフィルタできるようになりました。
-![TagでServer Groupに追加しようとする対象をフィルタリングした例](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20251010-084037.png) +TagでServer Groupに追加しようとする対象をフィルタリングした例
TagでServer Groupに追加しようとする対象をフィルタリングした例
@@ -90,7 +90,7 @@ Test ConnectionはServer Groupを保存した後にのみ使用できます。 #### 3. Accounts登録
-![Screenshot-2025-07-27-at-10.33.48-PM.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/Screenshot-2025-07-27-at-10.33.48-PM.png) +Screenshot-2025-07-27-at-10.33.48-PM.png
1. 該当コネクションにアクセス時に必要なAccountを登録し、管理します。Accountを登録する方法は2つあります。 @@ -99,11 +99,11 @@ Test ConnectionはServer Groupを保存した後にのみ使用できます。 2. または`Add Account`機能を利用して手動でAccountを追加できます。 1. `Add Account`ボタンクリック時、アカウント設定のためのモーダル窓が表記されます。選択したCategoryごとに入力しなければならない項目が異なります。
- ![Screenshot-2025-07-27-at-10.37.35-PM.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/Screenshot-2025-07-27-at-10.37.35-PM.png) + Screenshot-2025-07-27-at-10.37.35-PM.png
2. Provisioningアカウントで指定されたアカウントはAccount横に鍵アイコンが表示されます。
- ![Screenshot-2025-07-27-at-10.35.23-PM.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/Screenshot-2025-07-27-at-10.35.23-PM.png) + Screenshot-2025-07-27-at-10.35.23-PM.png
3. カテゴリ別でアカウントを設定できます。 1. Category : 最も先にアカウントの認証方式とタイプを定義するCategoryを選択する必要があります。選択するCategoryに応じて下段に表示される設定項目が動的に変更されます。 @@ -200,7 +200,7 @@ macOSのVNCプロトコル制限により、VNCを通じた自動ログインを #### 4. Server Group Owner登録
-![image-20250512-105127.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20250512-105127.png) +image-20250512-105127.png
サーバーグループオーナーを登録してWorkflowの承認者で指定できます。 @@ -214,7 +214,7 @@ macOSのVNCプロトコル制限により、VNCを通じた自動ログインを #### 5. Server Group Member登録
-![image-20250512-105142.png](/administrator-manual/servers/connection-management/server-groups/managing-servers-as-groups/image-20250512-105142.png) +image-20250512-105142.png
サーバーグループメンバーを登録して利用者別Workflowで表示されるServer Groupを指定できます。 diff --git a/src/content/ja/administrator-manual/servers/connection-management/servers.mdx b/src/content/ja/administrator-manual/servers/connection-management/servers.mdx index 4f70a78c..50906465 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/servers.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/servers.mdx @@ -12,7 +12,7 @@ QueryPieではServer資産に対する照会、作成、修正削除をサポー Cloud Providerを通じて同期してきたサーバー、APIまたは手動で登録したサーバーすべて同じページで管理します。
-![Administrator > Servers > Connection Management > Servers](/administrator-manual/servers/connection-management/servers/image-20240902-045519.png) +Administrator > Servers > Connection Management > Servers
Administrator > Servers > Connection Management > Servers
@@ -46,7 +46,7 @@ Administrator > Servers > Connection Management > Servers ### Server削除
-![image-20240723-162214.png](/administrator-manual/servers/connection-management/servers/image-20240723-162214.png) +image-20240723-162214.png
1. Administrator > Servers > Connection Management > Serversメニューに移動します。 diff --git a/src/content/ja/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx b/src/content/ja/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx index e0cacffc..86506998 100644 --- a/src/content/ja/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx +++ b/src/content/ja/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers.mdx @@ -16,7 +16,7 @@ QueryPieでは、アクセス制御を適用するサーバーを手動で登録 個別サーバーを手動で登録するためには、サーバーの基本的な情報入力が必要です。
-![Administrator > Servers > Connection Management > Servers > Create Server](/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers/image-20240828-154238.png) +Administrator > Servers > Connection Management > Servers > Create Server
Administrator > Servers > Connection Management > Servers > Create Server
@@ -25,7 +25,7 @@ Administrator > Servers > Connection Management > Servers > Create S #### 1. Information入力
-![image-20240828-154305.png](/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers/image-20240828-154305.png) +image-20240828-154305.png
1. Administrator > Servers > Connection Management > Serversメニューに移動します。 @@ -44,7 +44,7 @@ Administrator > Servers > Connection Management > Servers > Create S #### 2. Tag入力 (Optional)
-![image-20240723-163036.png](/administrator-manual/servers/connection-management/servers/manually-registering-individual-servers/image-20240723-163036.png) +image-20240723-163036.png
必要時、個別サーバーにTagを手動で入力できます。 diff --git a/src/content/ja/administrator-manual/servers/sac-general-configurations.mdx b/src/content/ja/administrator-manual/servers/sac-general-configurations.mdx index 72ae8039..3ed10525 100644 --- a/src/content/ja/administrator-manual/servers/sac-general-configurations.mdx +++ b/src/content/ja/administrator-manual/servers/sac-general-configurations.mdx @@ -26,7 +26,7 @@ Configurationsページは、QueryPieでサーバーアクセスとセキュリ 基本的なセキュリティ設定を管理します。
-![image-20251218-084954.png](/administrator-manual/servers/sac-general-configurations/image-20251218-084954.png) +image-20251218-084954.png
@@ -68,7 +68,7 @@ Configurationsページは、QueryPieでサーバーアクセスとセキュリ * User/Groupに付与されたRoleまたはDirect Permissionより優先適用 * `Add Configuration`ボタンクリック時、モーダルが生成され、以下の情報を記入して`Add`ボタンをクリックして追加（右上の`Save Changes`ボタンクリック以前まで未反映）
- ![image-20240829-095257.png](/administrator-manual/servers/sac-general-configurations/image-20240829-095257.png) + image-20240829-095257.png
* **Server Tag Key** : サーバータグキーを記入し、一度に一つずつのみ適用可能（使用時記入必須） * **Server Tag Value** : サーバータグバリューを記入し、一度に一つずつのみ適用可能（使用時記入必須） @@ -121,7 +121,7 @@ Workflow要求を通じたDirect Permission割り当て時に適用されるサ
-![Screenshot-2025-07-22-at-3.09.36-PM.png](/administrator-manual/servers/sac-general-configurations/Screenshot-2025-07-22-at-3.09.36-PM.png) +Screenshot-2025-07-22-at-3.09.36-PM.png
* Maximum Access Duration : サーバーアクセス権限の最大使用期間を設定 @@ -158,7 +158,7 @@ Workflow要求を通じたDirect Permission割り当て時に適用されるサ
-![Screenshot-2025-07-22-at-3.15.31-PM.png](/administrator-manual/servers/sac-general-configurations/Screenshot-2025-07-22-at-3.15.31-PM.png) +Screenshot-2025-07-22-at-3.15.31-PM.png
* **Maximum Access Duration** : 特権使用の最大持続期間を設定 diff --git a/src/content/ja/administrator-manual/servers/server-access-control/access-control.mdx b/src/content/ja/administrator-manual/servers/server-access-control/access-control.mdx index e4e47650..3a73d12e 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/access-control.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/access-control.mdx @@ -10,7 +10,7 @@ title: 'Access Control' Access Controlは、サーバーアクセス権限を付与し適用するための最終段階を意味します。
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/servers/server-access-control/access-control/image-20240902-051205.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
diff --git a/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx b/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx index f4dadf29..49318f62 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions.mdx @@ -17,7 +17,7 @@ import { Callout } from 'nextra/components' #### 1. 権限を付与する対象を選択します。
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/image-20240828-015212.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
@@ -29,7 +29,7 @@ Administrator > Servers > Server Access Control > Access Control #### 2.**[Step 1]**: 権限を付与するサーバーまたはサーバーグループのアカウントを選択します。
-![Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 1](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/image-20240828-015324.png) +Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 1
Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 1
@@ -49,7 +49,7 @@ Grant Permissions Step 1でサーバーは最大1000個までしか表示され #### 3.**[Step 2]**: 選択したサーバーに対するアクセス可能ポリシーを設定します。
-![Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 2](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/Screenshot-2025-07-27-at-5.28.54-PM.png) +Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 2
Administrator > Servers > Server Access Control > Access Control > Details > Grant Permissions Step 2
@@ -89,7 +89,7 @@ Administrator > Servers > Server Access Control > Access Control > D ### Access Control権限回収
-![Administrator > Servers > Server Access Control > Access Control > Servers](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-permissions/image-20240421-025726.png) +Administrator > Servers > Server Access Control > Access Control > Servers
Administrator > Servers > Server Access Control > Access Control > Servers
diff --git a/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx b/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx index 203d95f0..bca1d356 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles.mdx @@ -16,7 +16,7 @@ import { Callout } from 'nextra/components' #### 1. 権限を付与する対象を選択します。
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-051928.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
@@ -28,7 +28,7 @@ Administrator > Servers > Server Access Control > Access Control #### 2. 権限を付与するRoleを選択します。
-![Administrator > Servers > Server Access Control > Access Control > List Details > Rolesタブ](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-051957.png) +Administrator > Servers > Server Access Control > Access Control > List Details > Rolesタブ
Administrator > Servers > Server Access Control > Access Control > List Details > Rolesタブ
@@ -37,7 +37,7 @@ Administrator > Servers > Server Access Control > Access Control > L 1. 画面左中央のRolesタブを選択します。 2. 右中央で`+ Grant Roles`ボタンをクリックします。
- ![image-20240902-052029.png](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-052029.png) + image-20240902-052029.png
3. 付与するRole左チェックボックスにチェックします。 4. Expiration Dateを入力します。基本値は1年です。 @@ -47,7 +47,7 @@ Administrator > Servers > Server Access Control > Access Control > L ### Role回収
-![Server Settings > Server Access Control > Access Control > List Details > Rolesタブ](/administrator-manual/servers/server-access-control/access-control/granting-and-revoking-roles/image-20240902-052047.png) +Server Settings > Server Access Control > Access Control > List Details > Rolesタブ
Server Settings > Server Access Control > Access Control > List Details > Rolesタブ
diff --git a/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx b/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx index 7d235274..82827c30 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/access-control/granting-server-privilege.mdx @@ -15,7 +15,7 @@ PermissionまたはRoleでアクセス権限が付与されたサーバーに対 ### Server Privilege付与
-![Administrator > Servers > Server Access Control > Access Control > User/Group > Servers > Server Details](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/image-20250307-121546.png) +Administrator > Servers > Server Access Control > Access Control > User/Group > Servers > Server Details
Administrator > Servers > Server Access Control > Access Control > User/Group > Servers > Server Details
@@ -37,19 +37,19 @@ Administrator > Servers > Server Access Control > Access Control > U 6. モーダルの項目はサーバーのOSとRequire Privilegeオプション状態に応じて表示される項目が異なります。 1. サーバーのOSがLinuxでRequire Privilegeオプションが有効化された場合
- ![Screenshot-2025-07-02-at-5.14.50-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-02-at-5.14.50-PM.png) + Screenshot-2025-07-02-at-5.14.50-PM.png
2. サーバーのOSがLinuxでRequire Privilegeオプションが無効化された場合
- ![Screenshot-2025-07-01-at-5.58.34-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-01-at-5.58.34-PM.png) + Screenshot-2025-07-01-at-5.58.34-PM.png
3. サーバーのOSがLinuxでなくRequire Privilegeオプションが有効化された場合
- ![Screenshot-2025-07-01-at-6.02.23-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-01-at-6.02.23-PM.png) + Screenshot-2025-07-01-at-6.02.23-PM.png
4. サーバーのOSがLinuxでなくRequire Privilegeオプションが無効化された場合
- ![Screenshot-2025-07-02-at-5.10.49-PM.png](/administrator-manual/servers/server-access-control/access-control/granting-server-privilege/Screenshot-2025-07-02-at-5.10.49-PM.png) + Screenshot-2025-07-02-at-5.10.49-PM.png
diff --git a/src/content/ja/administrator-manual/servers/server-access-control/blocked-accounts.mdx b/src/content/ja/administrator-manual/servers/server-access-control/blocked-accounts.mdx index 7d7d020f..5e4e0682 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/blocked-accounts.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/blocked-accounts.mdx @@ -14,7 +14,7 @@ title: 'Blocked Accounts' ### サーバーアカウント有効化
-![Administrator > Servers > Server Access Control > Blocked Accounts](/administrator-manual/servers/server-access-control/blocked-accounts/image-20240902-053139.png) +Administrator > Servers > Server Access Control > Blocked Accounts
Administrator > Servers > Server Access Control > Blocked Accounts
diff --git a/src/content/ja/administrator-manual/servers/server-access-control/command-templates.mdx b/src/content/ja/administrator-manual/servers/server-access-control/command-templates.mdx index a526b379..2f199307 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/command-templates.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/command-templates.mdx @@ -14,7 +14,7 @@ import { Callout } from 'nextra/components' また、サーバー特権申請プロセスでユーザーが選択できるコマンドリストを標準化して管理効率性を高めることができます。
-![Administrator > Servers > Server Access Control > Command Templates](/administrator-manual/servers/server-access-control/command-templates/image-20240902-053009.png) +Administrator > Servers > Server Access Control > Command Templates
Administrator > Servers > Server Access Control > Command Templates
@@ -26,7 +26,7 @@ Administrator > Servers > Server Access Control > Command Templates 設定方法は[サーバーアクセスポリシー設定](policies/setting-server-access-policy)の **commandsRef** 部分を参照します。
-![Administrator > Servers > Server Access Control > Command Templates > Create Command Template](/administrator-manual/servers/server-access-control/command-templates/Screenshot-2025-07-22-at-3.23.24-PM.png) +Administrator > Servers > Server Access Control > Command Templates > Create Command Template
Administrator > Servers > Server Access Control > Command Templates > Create Command Template
diff --git a/src/content/ja/administrator-manual/servers/server-access-control/policies.mdx b/src/content/ja/administrator-manual/servers/server-access-control/policies.mdx index d36e3b0c..ec3b832c 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/policies.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/policies.mdx @@ -12,7 +12,7 @@ QueryPieサーバーアクセスポリシー（Policy）は、組織で管理す サーバーまたはサーバーグループ別にいつ接続を許可するか、どのコマンドを禁止するかなど、詳細なポリシーを適用してユーザーまたはグループ別に業務用途に合わせて最小限のサーバーにのみアクセスできるように設定できます。
-![Administrator > Servers > Server Access Control > Policies](/administrator-manual/servers/server-access-control/policies/image-20240902-052616.png) +Administrator > Servers > Server Access Control > Policies
Administrator > Servers > Server Access Control > Policies
@@ -30,7 +30,7 @@ Administrator > Servers > Server Access Control > Policies ### Policyの照会
-![Administrator > Servers > Server Access Control > Policies > List Details](/administrator-manual/servers/server-access-control/policies/image-20240902-052643.png) +Administrator > Servers > Server Access Control > Policies > List Details
Administrator > Servers > Server Access Control > Policies > List Details
@@ -42,7 +42,7 @@ Administrator > Servers > Server Access Control > Policies > List De #### Detailタブ
-![screenshot-20240808-171818.png](/administrator-manual/servers/server-access-control/policies/screenshot-20240808-171818.png) +screenshot-20240808-171818.png
1. デフォルトで指定されるタブでポリシーで定義されたコードを照会できます。 @@ -52,7 +52,7 @@ Administrator > Servers > Server Access Control > Policies > List De #### Rolesタブ
-![image-20240723-115930.png](/administrator-manual/servers/server-access-control/policies/image-20240723-115930.png) +image-20240723-115930.png
1. 該当ポリシーが割り当てられているRoleリストを列挙します。 @@ -66,7 +66,7 @@ Administrator > Servers > Server Access Control > Policies > List De #### Versionsタブ
-![image-20240723-120008.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120008.png) +image-20240723-120008.png
1. 該当ポリシーの各バージョンに対する履歴を列挙します。 @@ -85,14 +85,14 @@ Administrator > Servers > Server Access Control > Policies > List De 6. 下部に当時の **ポリシーコードスナップショット** が表示されます。
-![image-20240723-120033.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120033.png) +image-20240723-120033.png
### Policyの作成
-![image-20240723-120134.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120134.png) +image-20240723-120134.png
1. Administrator > Servers > Server Access Control > Policiesメニューに移動します。 @@ -106,7 +106,7 @@ Administrator > Servers > Server Access Control > Policies > List De ### Policyの編集
-![image-20240723-120317.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120317.png) +image-20240723-120317.png
1. Administrator > Servers > Server Access Control > Policiesメニューに移動します。 @@ -120,7 +120,7 @@ Administrator > Servers > Server Access Control > Policies > List De ### Policyの削除
-![image-20240723-120357.png](/administrator-manual/servers/server-access-control/policies/image-20240723-120357.png) +image-20240723-120357.png
1. Administrator > Servers > Server Access Control > Policiesメニューに移動します。 diff --git a/src/content/ja/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx b/src/content/ja/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx index 1da76556..84b9d519 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/policies/setting-server-access-policy.mdx @@ -35,7 +35,7 @@ PolicyはIaCのような形態でYAML Codeをベースに動作します。 ### Policyコードの編集
-![Administrator > Servers > Server Access Control > Policies > List Details > Go to Editor Mode](/administrator-manual/servers/server-access-control/policies/setting-server-access-policy/Screenshot-2025-07-27-at-5.40.59-PM.png) +Administrator > Servers > Server Access Control > Policies > List Details > Go to Editor Mode
Administrator > Servers > Server Access Control > Policies > List Details > Go to Editor Mode
diff --git a/src/content/ja/administrator-manual/servers/server-access-control/roles.mdx b/src/content/ja/administrator-manual/servers/server-access-control/roles.mdx index 87e6f2b2..97dc776f 100644 --- a/src/content/ja/administrator-manual/servers/server-access-control/roles.mdx +++ b/src/content/ja/administrator-manual/servers/server-access-control/roles.mdx @@ -13,7 +13,7 @@ import { Callout } from 'nextra/components' Roleは複数のポリシーを総合して単一役割で定義するのに使用されます。
-![Administrator > Servers > Server Access Control > Roles](/administrator-manual/servers/server-access-control/roles/image-20240902-052135.png) +Administrator > Servers > Server Access Control > Roles
Administrator > Servers > Server Access Control > Roles
@@ -34,7 +34,7 @@ Administrator > Servers > Server Access Control > Roles ### Roleの照会
-![Administrator > Servers > Server Access Control > Roles > List Details](/administrator-manual/servers/server-access-control/roles/image-20240902-052205.png) +Administrator > Servers > Server Access Control > Roles > List Details
Administrator > Servers > Server Access Control > Roles > List Details
@@ -52,7 +52,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai 5. **Assigned By** : 該当ポリシーを割り当てた管理者名 3. 各ポリシー行をクリックすると該当ポリシーの詳細情報をドロワー形式で提供します。
- ![image-20240902-052235.png](/administrator-manual/servers/server-access-control/roles/image-20240902-052235.png) + image-20240902-052235.png
1. 上部には基本情報が以下のように表示されます： 1. **Name** : Policy名 @@ -64,7 +64,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai 2. 下部にはポリシーがコードで表示されます。 2. **Users/Groups**
- ![image-20240902-052352.png](/administrator-manual/servers/server-access-control/roles/image-20240902-052352.png) + image-20240902-052352.png
1. 該当Roleが付与されているユーザー/グループリストを列挙します。 2. ユーザー/グループ名で検索可能です。 @@ -76,7 +76,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai 5. **Granted At** : ユーザー/グループに該当Roleが付与された日時 3. **Servers**
- ![image-20240902-052432.png](/administrator-manual/servers/server-access-control/roles/image-20240902-052432.png) + image-20240902-052432.png
1. 該当Roleによってアクセス可能なサーバーリストを列挙します。 2. Server名で検索可能です。 @@ -89,7 +89,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai ### Roleの作成
-![image-20240723-081606.png](/administrator-manual/servers/server-access-control/roles/image-20240723-081606.png) +image-20240723-081606.png
1. Administrator > Servers > Server Access Control > Rolesメニューに移動します。 @@ -103,7 +103,7 @@ Administrator > Servers > Server Access Control > Roles > List Detai ### Roleの編集
-![Administrator > Servers > Server Access Control > Roles > List Details](/administrator-manual/servers/server-access-control/roles/image-20240902-052459.png) +Administrator > Servers > Server Access Control > Roles > List Details
Administrator > Servers > Server Access Control > Roles > List Details
diff --git a/src/content/ja/administrator-manual/servers/server-account-management/account-management.mdx b/src/content/ja/administrator-manual/servers/server-account-management/account-management.mdx index 3a6a935e..75f778a2 100644 --- a/src/content/ja/administrator-manual/servers/server-account-management/account-management.mdx +++ b/src/content/ja/administrator-manual/servers/server-account-management/account-management.mdx @@ -17,7 +17,7 @@ Password Provisioningを通じてパスワードが変更されたサーバー ### Accountの照会
-![Administrator > Servers > Server Account Management > Account Management ](/administrator-manual/servers/server-account-management/account-management/Screenshot-2025-07-27-at-6.47.45-PM.png) +Administrator > Servers > Server Account Management > Account Management
Administrator > Servers > Server Account Management > Account Management
@@ -41,7 +41,7 @@ Administrator > Servers > Server Account Management > Account Managemen ### One Time Accountの照会
-![Administrator > Servers > Server Account Management > Account Management > One Time Accountsタブ](/administrator-manual/servers/server-account-management/account-management/Screenshot-2025-07-27-at-6.50.29-PM.png) +Administrator > Servers > Server Account Management > Account Management > One Time Accountsタブ
Administrator > Servers > Server Account Management > Account Management > One Time Accountsタブ
@@ -62,7 +62,7 @@ Administrator > Servers > Server Account Management > Account Managemen ### Active Directoryの照会
-![Administrator > Servers > Server Account Management > Account Management > Active Directoryタブ](/administrator-manual/servers/server-account-management/account-management/Screenshot-2025-07-27-at-7.03.55-PM.png) +Administrator > Servers > Server Account Management > Account Management > Active Directoryタブ
Administrator > Servers > Server Account Management > Account Management > Active Directoryタブ
@@ -81,7 +81,7 @@ Administrator > Servers > Server Account Management > Account Managemen ### Account詳細情報の照会
-![image-20240831-155640.png](/administrator-manual/servers/server-account-management/account-management/image-20240831-155640.png) +image-20240831-155640.png
1. Administrator > Servers > Server Account Management > Account Managementメニューに移動します diff --git a/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning.mdx b/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning.mdx index a9fdca0c..0a6b1f88 100644 --- a/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning.mdx +++ b/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning.mdx @@ -19,7 +19,7 @@ import { Callout } from 'nextra/components' ### パスワード変更Job照会
-![Administrator > Servers > Server Account Management > Password Provisioning](/administrator-manual/servers/server-account-management/password-provisioning/Screenshot-2025-07-27-at-6.31.29-PM.png) +Administrator > Servers > Server Account Management > Password Provisioning
Administrator > Servers > Server Account Management > Password Provisioning
@@ -39,7 +39,7 @@ Administrator > Servers > Server Account Management > Password Provisio ### Active Directoryパスワード変更Job照会
-![Administrator > Servers > Server Account Management > Password Provisioning](/administrator-manual/servers/server-account-management/password-provisioning/Screenshot-2025-07-27-at-6.33.43-PM.png) +Administrator > Servers > Server Account Management > Password Provisioning
Administrator > Servers > Server Account Management > Password Provisioning
@@ -58,7 +58,7 @@ Administrator > Servers > Server Account Management > Password Provisio ### Active Directoryパスワード変更
-![Screenshot-2025-07-27-at-7.22.21-PM.png](/administrator-manual/servers/server-account-management/password-provisioning/Screenshot-2025-07-27-at-7.22.21-PM.png) +Screenshot-2025-07-27-at-7.22.21-PM.png
1. Administrator > Servers > Server Account Management > Password Provisioning > Active Directoryタブ > パスワード詳細画面に移動します。 @@ -74,7 +74,7 @@ Administrator > Servers > Server Account Management > Password Provisio ### パスワード変更Job削除
-![image-20240831-161802.png](/administrator-manual/servers/server-account-management/password-provisioning/image-20240831-161802.png) +image-20240831-161802.png
1. Administrator > Servers > Server Account Management > Password Provisioningメニューに移動します。 diff --git a/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx b/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx index bac41dcf..3f15626f 100644 --- a/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx +++ b/src/content/ja/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job.mdx @@ -20,7 +20,7 @@ QueryPieを通じたサーバーアカウントのパスワード変更のため ### パスワード変更Job生成
-![Administrator > Servers > Server Account Management > Password Provisioning > Create Job](/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job/image-20240831-162006.png) +Administrator > Servers > Server Account Management > Password Provisioning > Create Job
Administrator > Servers > Server Account Management > Password Provisioning > Create Job
@@ -45,7 +45,7 @@ Provisioning Informationアカウントのパスワードを周期的に変更 ### Active Directoryパスワード変更Job生成
-![Administrator > Servers > Server Account Management > Password Provisioning > Active Directoryタブ > Create Job](/administrator-manual/servers/server-account-management/password-provisioning/creating-password-change-job/Screenshot-2025-07-27-at-6.26.06-PM.png) +Administrator > Servers > Server Account Management > Password Provisioning > Active Directoryタブ > Create Job
Administrator > Servers > Server Account Management > Password Provisioning > Active Directoryタブ > Create Job
diff --git a/src/content/ja/administrator-manual/servers/server-account-management/server-account-templates.mdx b/src/content/ja/administrator-manual/servers/server-account-management/server-account-templates.mdx index 7acee5ef..5994e553 100644 --- a/src/content/ja/administrator-manual/servers/server-account-management/server-account-templates.mdx +++ b/src/content/ja/administrator-manual/servers/server-account-management/server-account-templates.mdx @@ -13,7 +13,7 @@ title: 'Server Account Templates' ### サーバーアカウントテンプレート生成
-![Administrator > Servers > Server Account Management > Server Account Templates > Create Template](/administrator-manual/servers/server-account-management/server-account-templates/image-20240828-011910.png) +Administrator > Servers > Server Account Management > Server Account Templates > Create Template
Administrator > Servers > Server Account Management > Server Account Templates > Create Template
@@ -28,7 +28,7 @@ Administrator > Servers > Server Account Management > Server Account Te 5. リストで新しく生成されたテンプレートをクリックします。 6. Account項目で`Add Account`をクリックしてテンプレートに登録するアカウントを追加します。
- ![Screenshot-2025-07-27-at-10.35.23-PM.png](/administrator-manual/servers/server-account-management/server-account-templates/Screenshot-2025-07-27-at-10.35.23-PM.png) + Screenshot-2025-07-27-at-10.35.23-PM.png
* 個別Account設定方法は[サーバーをグループで管理](../connection-management/server-groups/managing-servers-as-groups)を参考にします。 7. 右上の`Save Changes`をクリックして保存します。 diff --git a/src/content/ja/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx b/src/content/ja/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx index efe805fa..278c0a0d 100644 --- a/src/content/ja/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx +++ b/src/content/ja/administrator-manual/servers/server-account-management/ssh-key-configurations.mdx @@ -13,7 +13,7 @@ title: 'SSH Key Configurations' ### SSH Key登録
-![Administrator > Servers > Server Account Management > SSH Key Configurations > Create SSH Key](/administrator-manual/servers/server-account-management/ssh-key-configurations/image-20240828-012337.png) +Administrator > Servers > Server Account Management > SSH Key Configurations > Create SSH Key
Administrator > Servers > Server Account Management > SSH Key Configurations > Create SSH Key
@@ -33,7 +33,7 @@ Administrator > Servers > Server Account Management > SSH Key Configura ### SSH Key管理機能
-![Administrator > Servers > Server Account Management > SSH Key Configurations > SSH Key Details](/administrator-manual/servers/server-account-management/ssh-key-configurations/image-20240828-012530.png) +Administrator > Servers > Server Account Management > SSH Key Configurations > SSH Key Details
Administrator > Servers > Server Account Management > SSH Key Configurations > SSH Key Details
diff --git a/src/content/ja/administrator-manual/servers/session-monitoring.mdx b/src/content/ja/administrator-manual/servers/session-monitoring.mdx index a9ca6d04..1a427a2d 100644 --- a/src/content/ja/administrator-manual/servers/session-monitoring.mdx +++ b/src/content/ja/administrator-manual/servers/session-monitoring.mdx @@ -18,7 +18,7 @@ QueryPieを通じたサーバー接続セッションを照会できます。 ### Session Monitoring照会
-![Administrator > Servers > Monitoring > Session Monitoring](/administrator-manual/servers/session-monitoring/image-20251218-073053.png) +Administrator > Servers > Monitoring > Session Monitoring
Administrator > Servers > Monitoring > Session Monitoring
@@ -42,7 +42,7 @@ Administrator > Servers > Monitoring > Session Monitoring ### Session強制終了
-![image-20251218-073257.png](/administrator-manual/servers/session-monitoring/image-20251218-073257.png) +image-20251218-073257.png
diff --git a/src/content/ja/administrator-manual/web-apps.mdx b/src/content/ja/administrator-manual/web-apps.mdx index 0e85ae75..e0978a3f 100644 --- a/src/content/ja/administrator-manual/web-apps.mdx +++ b/src/content/ja/administrator-manual/web-apps.mdx @@ -5,7 +5,7 @@ title: 'Web Apps' # Web Apps
-![image-20241218-141244.png](/administrator-manual/web-apps/image-20241218-141244.png) +image-20241218-141244.png
### Overview diff --git a/src/content/ja/administrator-manual/web-apps/connection-management/web-app-configurations.mdx b/src/content/ja/administrator-manual/web-apps/connection-management/web-app-configurations.mdx index fa47a316..e22e35db 100644 --- a/src/content/ja/administrator-manual/web-apps/connection-management/web-app-configurations.mdx +++ b/src/content/ja/administrator-manual/web-apps/connection-management/web-app-configurations.mdx @@ -11,7 +11,7 @@ Web App Configurationsページは、QueryPie WACでウェブアプリケーシ これにより、管理者は組織のセキュリティ要件に合わせてウェブ環境を構成し、全体的な脅威からシステムを保護できます。
-![Administrator > Web Apps > Connection Management > Web App Configurations](/administrator-manual/web-apps/connection-management/web-app-configurations/image-20250629-153047.png) +Administrator > Web Apps > Connection Management > Web App Configurations
Administrator > Web Apps > Connection Management > Web App Configurations
diff --git a/src/content/ja/administrator-manual/web-apps/connection-management/web-apps.mdx b/src/content/ja/administrator-manual/web-apps/connection-management/web-apps.mdx index 08e791f7..2f0d3e59 100644 --- a/src/content/ja/administrator-manual/web-apps/connection-management/web-apps.mdx +++ b/src/content/ja/administrator-manual/web-apps/connection-management/web-apps.mdx @@ -12,7 +12,7 @@ QueryPieでは、Web Apps資産に対する照会、生成、修正事例をサ ウェブアプリケーションを通じて登録されたウェブアプリ、APIまたは手動で登録したウェブアプリすべて同じページで管理します。
-![Administrator > Web Apps > Connection Management > Web Apps](/administrator-manual/web-apps/connection-management/web-apps/image-20250629-153743.png) +Administrator > Web Apps > Connection Management > Web Apps
Administrator > Web Apps > Connection Management > Web Apps
@@ -36,7 +36,7 @@ Administrator > Web Apps > Connection Management > Web Apps ### Web App生成
-![Administrator > Web Apps > Connection Management > Web Apps](/administrator-manual/web-apps/connection-management/web-apps/Screenshot-2025-08-27-at-6.58.08-PM.png) +Administrator > Web Apps > Connection Management > Web Apps
Administrator > Web Apps > Connection Management > Web Apps
@@ -56,7 +56,7 @@ Administrator > Web Apps > Connection Management > Web Apps ### Web App OwnerとMember設定
-![Administrator > Web Apps > Connection Management > Web Apps > Web App Owners](/administrator-manual/web-apps/connection-management/web-apps/Screenshot-2025-08-27-at-6.57.07-PM.png) +Administrator > Web Apps > Connection Management > Web Apps > Web App Owners
Administrator > Web Apps > Connection Management > Web Apps > Web App Owners
@@ -70,7 +70,7 @@ Web AppにOwnerとMemberを指定してJust-In-Time（JIT）アクセス要求 * 一人のユーザーがOwnerとMember権限を同時に持つことができ、この場合、要求上申と承認がすべて可能です。
-![Assign Owners画面](/administrator-manual/web-apps/connection-management/web-apps/Screenshot-2025-08-27-at-6.57.24-PM.png) +Assign Owners画面
Assign Owners画面
diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart.mdx index 3d76166b..9fa25a49 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart.mdx @@ -48,7 +48,7 @@ QueryPieホームページ（`www.querypie.com`）内の `/ko/resources` 配下 2. `Create a Web App` ボタンをクリックすると、Webアプリ登録ページへ移動します。
-![Admin > Web Apps > Create a Web App](/administrator-manual/web-apps/wac-quickstart/screenshot-20250412-225620.png) +Admin > Web Apps > Create a Web App
Admin > Web Apps > Create a Web App
@@ -95,7 +95,7 @@ Admin > Web Apps > Create a Web App 次に、QueryPieウェブサイトに対して、登録されたサブパスにのみアクセスを許可するポリシーを作成します。
-![Admin > Web Apps > Web App Access Control > Policies > Edit Policy Code](/administrator-manual/web-apps/wac-quickstart/screenshot-20250412-230727.png) +Admin > Web Apps > Web App Access Control > Policies > Edit Policy Code
Admin > Web Apps > Web App Access Control > Policies > Edit Policy Code
@@ -131,7 +131,7 @@ spec: 今度は新しいロールを作成し、先ほど作成したポリシーを割り当てます。
-![Admin > Web Apps > Web App Access Control > Roles > List Details](/administrator-manual/web-apps/wac-quickstart/screenshot-20250330-204911.png) +Admin > Web Apps > Web App Access Control > Roles > List Details
Admin > Web Apps > Web App Access Control > Roles > List Details
@@ -148,7 +148,7 @@ Admin > Web Apps > Web App Access Control > Roles > List Details 今度は今作成したQP Web Testロールを現在のユーザーに割り当ててみます。
-![Admin > Web Apps > Web App Access Control > Access Control > List Details](/administrator-manual/web-apps/wac-quickstart/screenshot-20250330-204937.png) +Admin > Web Apps > Web App Access Control > Access Control > List Details
Admin > Web Apps > Web App Access Control > Access Control > List Details
@@ -169,14 +169,14 @@ Admin > Web Apps > Web App Access Control > Access Control > List De 1. QueryPieにログインした状態で、上部右側のプロフィールボタンをクリックし、プロフィールメニューから Support > Download Web Secure ボタンをクリックします。

- ![QueryPie > Profile Menu](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-120321.png) + QueryPie > Profile Menu
QueryPie > Profile Menu
2. QueryPie Web Secure Downloadモーダルが開きます。 **A. Install Root CA Certificate** で、Step 1. のDownload Linkをクリックすると証明書ファイルのダウンロードが実行されます。

- ![QueryPie Web Secure Download](/administrator-manual/web-apps/wac-quickstart/screenshot-20250116-155957.png) + QueryPie Web Secure Download
QueryPie Web Secure Download
@@ -194,7 +194,7 @@ Admin > Web Apps > Web App Access Control > Access Control > List De 2. ページ右上の開発者モードトグルを有効にします。 3. 受け取ったExtensionファイルを **圧縮を解かない** 状態で、拡張機能エリアにドラッグします。

- ![Chrome > 拡張機能管理](/administrator-manual/web-apps/wac-quickstart/screenshot-20241219-192626.png) + Chrome > 拡張機能管理
Chrome > 拡張機能管理
@@ -202,7 +202,7 @@ Admin > Web Apps > Web App Access Control > Access Control > List De 4. 新しいタブでHost Configurationページが開きます。QueryPie Hostに現在使用中のQueryPieアドレスを貼り付けて、`Continue` ボタンをクリックします。 1. Host情報が有効であれば `Go to Dashboard` ボタンが表示されます。クリックすると新しいタブでQueryPieにアクセスします。
- ![Host Configurationページ](/administrator-manual/web-apps/wac-quickstart/screenshot-20241219-192931.png) + Host Configurationページ
Host Configurationページ
@@ -225,14 +225,14 @@ WAC拡張機能インストール前に開いていたタブについては管 3. ロール選択モーダルが表示されたら、QP Web Testを選択します。 2. Web App Dashboard内のMy Appsに先ほど登録したQueryPie Web Siteアプリアイコンが表示されるはずです。アイコンをクリックするとウェブサイトにアクセスします。

- ![QueryPie > Web Apps > Web App Dashboard](/administrator-manual/web-apps/wac-quickstart/screenshot-20250412-224323.png) + QueryPie > Web Apps > Web App Dashboard
QueryPie > Web Apps > Web App Dashboard
3. 初回アクセス時、現在のWebセッションが記録されていることを知らせる画面が表示されます。`Continue` ボタンをクリックしてウェブサイトにアクセスします。

- ![Web Session Monitoring Notification](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-113541.png) + Web Session Monitoring Notification
Web Session Monitoring Notification
@@ -240,7 +240,7 @@ WAC拡張機能インストール前に開いていたタブについては管 4. QueryPieホームページにウォーターマークが適用されていることを確認できます。
5. 許可されていないページ（例：Productsメニュー）にアクセスを試みると、ブロック案内画面にリダイレクトされます。
- ![ QueryPie Access Denied](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-113037.png) + QueryPie Access Denied
QueryPie Access Denied
@@ -252,7 +252,7 @@ WAC拡張機能インストール前に開いていたタブについては管
-![Admin > Audit > Web Apps > Web Access History](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-115604.png) +Admin > Audit > Web Apps > Web Access History
Admin > Audit > Web Apps > Web Access History
@@ -281,7 +281,7 @@ Web App作成時にUser Activity Recordingをオンにしないと記録が残
-![Admin > Audit > Web Apps > User Activity Recordings > Details](/administrator-manual/web-apps/wac-quickstart/screenshot-20241223-115805.png) +Admin > Audit > Web Apps > User Activity Recordings > Details
Admin > Audit > Web Apps > User Activity Recordings > Details
diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx index 4908b604..7a541a94 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide.mdx @@ -32,7 +32,7 @@ JIT権限取得Guideは `10.3.0` バージョンを基準に説明します。 2. `Create a Web App` ボタンをクリックすると、Webアプリ登録ページへ移動します。
-![screenshot-20250412-225620.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/screenshot-20250412-225620.png) +screenshot-20250412-225620.png
以下の情報を入力します。 @@ -56,7 +56,7 @@ JIT権限取得Guideは `10.3.0` バージョンを基準に説明します。 ### 2. Web App Owner / Memberの登録
-![image-20250513-042540.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-042540.png) +image-20250513-042540.png
1. Webアプリ詳細ページにアクセスします @@ -84,7 +84,7 @@ QueryPieを通じてWeb Appアクセス時、Root CA証明書インストール
-![image-20250513-065134.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-065134.png) +image-20250513-065134.png
1. QueryPieアクセス後、上部のWeb Appsをクリックします。 @@ -94,7 +94,7 @@ QueryPieを通じてWeb Appアクセス時、Root CA証明書インストール
-![image-20250513-065247.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-065247.png) +image-20250513-065247.png
1. Web App Just-In-Time Access Requestにアクセスします。 @@ -118,7 +118,7 @@ JIT（Just-in-Time）権限申請時、以下のような制約事項があり ### 4. 決裁権者のJIT Web Appアクセス権限要求承認
-![image-20250513-072925.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-072925.png) +image-20250513-072925.png
1. （Web App Ownerに指定された）決裁権を持つユーザーがWorkflowにアクセスします。 @@ -130,7 +130,7 @@ JIT（Just-in-Time）権限申請時、以下のような制約事項があり ### 5. QueryPieを通じたWebアプリへのアクセス
-![image-20250513-073501.png](/administrator-manual/web-apps/wac-quickstart/1030-wac-jit-permission-acquisition-guide/image-20250513-073501.png) +image-20250513-073501.png
1. QueryPie Web Appsに移動します。 diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx index 721221ca..cb864051 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations.mdx @@ -14,7 +14,7 @@ Web App Configurationsページは10.2.6またはそれ以上のバージョン Web App ConfigurationsページではWAC関連の初期設定をGUIで実行できます。
-![Admin > Web Apps > Connection Management > Web App Configurations](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250413-224538.png) +Admin > Web Apps > Connection Management > Web App Configurations
Admin > Web Apps > Connection Management > Web App Configurations
@@ -63,7 +63,7 @@ Current Version、Minimum Required Version情報はQueryPieで提供する互換 2. 閉鎖網環境でQueryPie > Web App Configurationsページに接続した後、QueryPie Web Secure (Extension) Configurationsセクションで `Edit` ボタンをクリックします。 3. Extension Fileオプションで `Add by File Upload` を選択し、ダウンロードしていたエクステンションファイルをアップロードします。
- ![Admin > Web Apps > Connection Management > Web App Configurations > WAC Secure 설정 모달](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250310-160708.png) + Admin > Web Apps > Connection Management > Web App Configurations > WAC Secure 설정 모달
Admin > Web Apps > Connection Management > Web App Configurations > WAC Secure 설정 모달
@@ -88,7 +88,7 @@ Watermark Configurationsセクションでは現在適用されたウォータ 1. 文句設定を変更するには `Edit` ボタンをクリックします。 2. 設定モーダルが開いた状態では現在接続したユーザーを基準にウォーターマーク適用結果をプレビューできます。

- ![Admin > Web Apps > Connection Management > Web App Configurations > 워터마크 설정 모달](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250310-161723.png) + Admin > Web Apps > Connection Management > Web App Configurations > 워터마크 설정 모달
Admin > Web Apps > Connection Management > Web App Configurations > 워터마크 설정 모달
@@ -103,7 +103,7 @@ Watermark Configurationsセクションでは現在適用されたウォータ Root CA Certificate ConfigurationsセクションではQueryPieで既存使用中のRoot CA証明書をバックアップし復元できます。
-![Admin > Web Apps > Connection Management > Web App Configurations > Manage .cer file モーダル](/administrator-manual/web-apps/wac-quickstart/initial-wac-setup-in-web-app-configurations/screenshot-20250413-225409.png) +Admin > Web Apps > Connection Management > Web App Configurations > Manage .cer file モーダル
Admin > Web Apps > Connection Management > Web App Configurations > Manage .cer file モーダル
diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx index 52e8ab70..1f9491ac 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide.mdx @@ -31,12 +31,12 @@ Webブラウザに以下のパスを入力すると、環境に適したRoot CA 2. キーチェーンアクセスアプリ画面に、ダウンロードした証明書ファイルをドラッグして貼り付けます。新規インストールされたquerypie証明書は信頼された状態ではありません。 3. querypie証明書をダブルクリックしてモーダルを開き、信頼項目をクリックして折りたたまれた領域を展開した後、**この証明書使用時** : `システム初期設定使用` を `常に信頼` に変更し、モーダルを閉じます。
- ![screenshot-20250113-201320.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-201320.png) + screenshot-20250113-201320.png
4. システム証明書信頼設定変更のために追加認証を実行します。 5. 新規インストールされたquerypie証明書はすべてのユーザーに対して信頼されたものとして表示されます。
- ![screenshot-20250113-201143.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-201143.png) + screenshot-20250113-201143.png
またはTerminalで以下のコマンドを実行して同様に設定できます。 @@ -53,24 +53,24 @@ sudo security add-trusted-cert -d -r trustRoot -k /Library/Keychains/System.keyc 2. 証明書ファイルに対して右クリックし、コンテキストメニューで `証明書インストール(I)` を選択して証明書インポートウィザードを開始します。 3. 証明書インポートウィザードウィンドウが開いたら、保存場所を `現在のユーザー(C)` で選択し、`次へ(N)` ボタンをクリックします。
- ![screenshot-20250113-202645.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-202645.png) + screenshot-20250113-202645.png
4. 証明書保存場所について、`すべての証明書を以下の保存場所に保存(P)` オプションを選択し、`参照(R)...` ボタンをクリックします。 5. **証明書保存場所選択** モーダルが開いたら、信頼できるルート証明機関を選択します。実際の保存場所表示オプションは解除状態を維持します。確認ボタンをクリックします。
- ![screenshot-20250113-202727.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-202727.png) + screenshot-20250113-202727.png
6. 証明書保存場所設定を確認し、`次へ(N)` ボタンをクリックします。
- ![screenshot-20250113-202738.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-202738.png) + screenshot-20250113-202738.png
7. 設定した内容を確認し、`完了(F)` ボタンを押します。
- ![screenshot-20250113-203130.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-203130.png) + screenshot-20250113-203130.png
8. セキュリティ警告モーダルが出力されます。`はい(Y)` ボタンを押すと即座に証明書インポートが実行されます。インポート完了モーダルで確認ボタンをクリックします。
- ![screenshot-20250113-203453.png](/administrator-manual/web-apps/wac-quickstart/root-ca-certificate-installation-guide/screenshot-20250113-203453.png) + screenshot-20250113-203453.png
### 3. Chrome証明書設定確認 diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx index 08923d70..08916381 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-faq.mdx @@ -19,7 +19,7 @@ WAC機能更新に従ってエクステンション更新が必須的な場合 #### レコーディング案内モーダルはいつ表示されるのですか？毎日表示されるようです。
-![image-20250414-105519.png](/administrator-manual/web-apps/wac-quickstart/wac-faq/image-20250414-105519.png) +image-20250414-105519.png
レコーディング案内モーダルはセッション開始時に表示されます。 @@ -46,7 +46,7 @@ WebアプリでUser Activity Recordingがオンになっており、スクロー #### エクステンションのユーザー情報がN/Aで表示され、リフレッシュしても変化がありません。
-![image-20250415-071521.png](/administrator-manual/web-apps/wac-quickstart/wac-faq/image-20250415-071521.png) +image-20250415-071521.png
エクステンションのログインが解除されて発生する現象です。 diff --git a/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx b/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx index 5b82264d..6ad656ce 100644 --- a/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx +++ b/src/content/ja/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide.mdx @@ -16,7 +16,7 @@ WACエクステンションインストール前に開いていたタブに対 #### WebAppに接続できず、ブラウザに`ERR_TIMED_OUT`エラーメッセージが表示される場合
-![image-20250401-011848.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-011848.png) +image-20250401-011848.png
ブラウザがWAC Proxyと接続できずに発生する現象の可能性があります。 @@ -24,7 +24,7 @@ WACエクステンションインストール前に開いていたタブに対 まずAdmin > Web Apps > Web app ConfigurationメニューでWAC Proxyアドレスがよく設定されているか確認します。
-![image-20250401-012042.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-012042.png) +image-20250401-012042.png
問題が発生したブラウザのローカルターミナルで以下のコマンドを実行してWAC Proxyに接続できるか確認します。 @@ -83,7 +83,7 @@ $ $ curl -v -k https://internal-proxy.querypie.io:7447 * Chromeブラウザで `chrome://net-export/` を開き、Start Overをクリックします。 (Optionsはデフォルト値の `Strip private information` を選択します。)
-![image-20250401-012452.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-012452.png) +image-20250401-012452.png
* Chromeブラウザで接続できないWebAppアドレスを入力して移動します。 @@ -97,7 +97,7 @@ $ $ curl -v -k https://internal-proxy.querypie.io:7447 * 左側Eventsメニューでネットワーク送受信内容を確認します。
-![image-20250401-012759.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/image-20250401-012759.png) +image-20250401-012759.png
@@ -144,10 +144,10 @@ QueryPie Web Secure（Extension）に問題が発生した場合、関連ログ 1. パネルリストで、 `QueryPie Web Secure` をクリックします。
- ![screenshot-20250116-134315.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/screenshot-20250116-134315.png) + screenshot-20250116-134315.png
2. 開発者ツールでログ抽出機能が実行されます。 `Export Log` ボタンをクリックするとquerypie-web-secure-logs.jsonファイルの別途保存が実行されます。 `保存` ボタンを押します。
- ![screenshot-20250116-134632.png](/administrator-manual/web-apps/wac-quickstart/wac-troubleshooting-guide/screenshot-20250116-134632.png) + screenshot-20250116-134632.png
3. 保存完了されたログをCSリクエスト時に一緒に添付します。 diff --git a/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control.mdx b/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control.mdx index 1d8ff31d..0c877125 100644 --- a/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control.mdx +++ b/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control.mdx @@ -10,7 +10,7 @@ title: 'Access Control' Access Controlは、ウェブアプリアクセス権限を実装し適用するための最終段階を意味します。
-![Administrator > Web Apps > Web App Access Control > Access Control](/administrator-manual/web-apps/web-app-access-control/access-control/image-20250629-155857.png) +Administrator > Web Apps > Web App Access Control > Access Control
Administrator > Web Apps > Web App Access Control > Access Control
@@ -20,7 +20,7 @@ Administrator > Web Apps > Web App Access Control > Access Control ### Access Control現状照会
-![Administrator > Web Apps > Web App Access Control > Access Control > List Details](/administrator-manual/web-apps/web-app-access-control/access-control/Screenshot-2025-08-25-at-9.37.07-PM.png) +Administrator > Web Apps > Web App Access Control > Access Control > List Details
Administrator > Web Apps > Web App Access Control > Access Control > List Details
@@ -33,7 +33,7 @@ Administrator > Web Apps > Web App Access Control > Access Control > 5. Access Controlリストで行をクリックすると対象ユーザー/グループに対する詳細ページに移動します。 1. **Roles**
- ![image-20250629-160303.png](/administrator-manual/web-apps/web-app-access-control/access-control/image-20250629-160303.png) + image-20250629-160303.png
1. デフォルトで指定されるタブで付与されたRoleリストを照会できます。 2. Role名で検索可能です。 @@ -58,7 +58,7 @@ Administrator > Web Apps > Web App Access Control > Access Control > 2. リスト左上に位置するRevokeボタンをクリックします。 3. 権限回収確認ウィンドウが現れたら内容を確認して確認ボタンをクリックして最終的に権限を回収します。
- ![image-20250617-151613.png](/administrator-manual/web-apps/web-app-access-control/access-control/image-20250617-151613.png) + image-20250617-151613.png
3. **Web Apps** 1. 付与されたRoleたちによってアクセス可能なウェブアプリリストを列挙します。 diff --git a/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx b/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx index 3a2910c7..20f81199 100644 --- a/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx +++ b/src/content/ja/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles.mdx @@ -15,7 +15,7 @@ import { Callout } from 'nextra/components' #### 1. 権限を付与する対象を選択します。
-![Administrator > Servers > Server Access Control > Access Control](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161238.png) +Administrator > Servers > Server Access Control > Access Control
Administrator > Servers > Server Access Control > Access Control
@@ -28,13 +28,13 @@ Administrator > Servers > Server Access Control > Access Control #### 2. 権限を付与するRoleを選択します。
-![image-20250629-161326.png](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161326.png) +image-20250629-161326.png
1. 画面左側のRolesタブを選択します。 2. 右側中央で `+ Grant Roles` ボタンをクリックします。
- ![image-20250629-161407.png](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161407.png) + image-20250629-161407.png
3. 付与するRoleの左側のチェックボックスをチェックします。 4. Expiration Dateを入力します。基本値は1年です。 @@ -44,7 +44,7 @@ Administrator > Servers > Server Access Control > Access Control ### Roleの回収
-![image-20250629-161437.png](/administrator-manual/web-apps/web-app-access-control/access-control/granting-and-revoking-roles/image-20250629-161437.png) +image-20250629-161437.png
1. Administrator > Web Apps > Web App Access Control > Access Control メニューへ移動します。 diff --git a/src/content/ja/administrator-manual/web-apps/web-app-access-control/policies.mdx b/src/content/ja/administrator-manual/web-apps/web-app-access-control/policies.mdx index 693f0962..ae2294bc 100644 --- a/src/content/ja/administrator-manual/web-apps/web-app-access-control/policies.mdx +++ b/src/content/ja/administrator-manual/web-apps/web-app-access-control/policies.mdx @@ -12,7 +12,7 @@ import { Callout } from 'nextra/components' Policyは、ウェブアプリケーションアクセス権限を実装し適用するための基盤となる核心段階です。
-![Administrator > Web Apps > Web App Access Control > Policies](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164449.png) +Administrator > Web Apps > Web App Access Control > Policies
Administrator > Web Apps > Web App Access Control > Policies
@@ -21,7 +21,7 @@ Administrator > Web Apps > Web App Access Control > Policies ### Policyの照会
-![Administrator > Web Apps > Web App Access Control > Policies > List Details](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164509.png) +Administrator > Web Apps > Web App Access Control > Policies > List Details
Administrator > Web Apps > Web App Access Control > Policies > List Details
@@ -35,13 +35,13 @@ Administrator > Web Apps > Web App Access Control > Policies > List 6. 各行をクリックするとポリシー詳細情報照会が可能です。 1. Detail
- ![image-20250629-164600.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164600.png) + image-20250629-164600.png
1. デフォルトで指定されるタブでポリシーで定義されたコードを照会できます。 2. Detailタブの右側にある`Go to Editor Mode`ボタンをクリックすると、該当Code Editorページ画面に切り替わります。 2. Roles
- ![image-20250629-164733.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164733.png) + image-20250629-164733.png
1. 該当ポリシーが割り当てられているRoleリストを列挙します。 2. リストは各Roleごとに以下の情報を表示します： @@ -52,7 +52,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List 3. 各行をクリックするとRoleに対する詳細情報をドロワー形式で提供します。 3. Versions
- ![image-20250629-164755.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164755.png) + image-20250629-164755.png
1. 該当ポリシーの各バージョンに対する履歴を列挙します。 1. ポリシーバージョンはCodeが修正されて保存されると更新されます。 @@ -72,7 +72,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Policyの生成
-![image-20250629-164901.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164901.png) +image-20250629-164901.png
1. Administrator > Web Apps > Web App Access Control > Policiesメニューへ移動します。 @@ -85,7 +85,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Policyの修正
-![image-20250629-164928.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164928.png) +image-20250629-164928.png
@@ -97,7 +97,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Policyの複製
-![image-20250629-164941.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164941.png) +image-20250629-164941.png
1. Administrator > Web Apps > Web App Access Control > Policiesメニューに移動します。 @@ -109,7 +109,7 @@ Administrator > Web Apps > Web App Access Control > Policies > List ### Policyの削除
-![image-20250629-164955.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-164955.png) +image-20250629-164955.png
1. Administrator > Web Apps > Web App Access Control > Policiesメニューに移動します。 @@ -123,7 +123,7 @@ Policy削除時、該当ポリシーが付与されていたウェブアプリ ### Policyコードの編集
-![image-20250629-165051.png](/administrator-manual/web-apps/web-app-access-control/policies/image-20250629-165051.png) +image-20250629-165051.png
1. Administrator > Web Apps > Web App Access Control > Policiesメニューに移動します。 diff --git a/src/content/ja/administrator-manual/web-apps/web-app-access-control/roles.mdx b/src/content/ja/administrator-manual/web-apps/web-app-access-control/roles.mdx index 1ac34765..15c6138d 100644 --- a/src/content/ja/administrator-manual/web-apps/web-app-access-control/roles.mdx +++ b/src/content/ja/administrator-manual/web-apps/web-app-access-control/roles.mdx @@ -12,7 +12,7 @@ import { Callout } from 'nextra/components' Roleは、ウェブアプリアクセス権限を実装し適用するためのPolicy以降の段階として、Policyの集合であり、ユーザー/グループとポリシーの接続点となる権限を意味します。
-![Administrator > Web Apps > Web App Access Control > Roles](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-161837.png) +Administrator > Web Apps > Web App Access Control > Roles
Administrator > Web Apps > Web App Access Control > Roles
@@ -22,7 +22,7 @@ Administrator > Web Apps > Web App Access Control > Roles ### Roleの照会
-![Administrator > Web Apps > Web App Access Control > Roles > List Details](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-161857.png) +Administrator > Web Apps > Web App Access Control > Roles > List Details
Administrator > Web Apps > Web App Access Control > Roles > List Details
@@ -35,7 +35,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 5. 各行をクリックすると役割詳細情報照会が可能です。 1. **Policies**
- ![image-20250629-163153.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163153.png) + image-20250629-163153.png
1. デフォルトで指定されるタブで割り当てられたポリシーリストを照会できます。 2. テーブルリストには各ポリシー別以下の情報を表示します： @@ -46,7 +46,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 5. Assigned By：該当ポリシーを割り当てた管理者名 3. 各ポリシー行の左側ポリシーの詳細情報をドロワー形式で提供します。
- ![image-20250629-163327.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163327.png) + image-20250629-163327.png
1. 上部には基本情報が以下のように表示されます： 1. **Name** : Policy名 @@ -58,7 +58,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 2. 下部にはポリシーがコードで表示されます。 2. **Users/Groups**
- ![image-20250629-163722.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163722.png) + image-20250629-163722.png
1. 該当Roleが付与されているユーザー/グループリストを列挙します。 2. ユーザー/グループ名で検索可能です。 @@ -70,7 +70,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det 5. Granted At：ユーザー/グループに該当Roleが付与された日時 3. **Web Apps**
- ![image-20250629-163658.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163658.png) + image-20250629-163658.png
1. 該当Roleによってアクセス可能なウェブアプリケーションリストを列挙します。 2. ウェブアプリケーション名で検索可能です。 @@ -96,7 +96,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det ### Roleの修正
-![image-20250629-163924.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163924.png) +image-20250629-163924.png
1. Administrator > Web Apps > Access Control > Rolesメニューへ移動します。 @@ -107,7 +107,7 @@ Administrator > Web Apps > Web App Access Control > Roles > List Det ### Roleの削除
-![image-20250629-163949.png](/administrator-manual/web-apps/web-app-access-control/roles/image-20250629-163949.png) +image-20250629-163949.png
1. Administrator > Web Apps > Access Control > Rolesメニューへ移動します。 diff --git a/src/content/ja/installation.mdx b/src/content/ja/installation.mdx index db8fe83a..bb203864 100644 --- a/src/content/ja/installation.mdx +++ b/src/content/ja/installation.mdx @@ -9,11 +9,11 @@ QueryPie ACPはすべてのバージョンに対して事前ビルドされたDo 詳細なインストール案内は次の文書を参照してください： -* [インストール前の準備事項](installation/prerequisites) -* [インストール](installation/installation) -* [システムアーキテクチャとネットワークアクセス制御](installation/system-architecture-and-network-access-control) -* [コンテナ環境変数](installation/container-environment-variables) -* [ライセンスインストール](installation/license-installation) -* [サーバー構成要件](installation/server-configuration-requirements) -* [QueryPie ACP Community Edition](installation/querypie-acp-community-edition) - * [MCP設定ガイド](installation/querypie-acp-community-edition/mcp-configuration-guide) +* [설치 전 준비사항](#unexpected-failure) +* [설치하기](#unexpected-failure) +* [시스템 아키텍처와 네트워크 접근제어](#unexpected-failure) +* [컨테이너 환경변수](#unexpected-failure) +* [라이선스 설치](#unexpected-failure) +* [서버구성 요구사항](#unexpected-failure) +* [QueryPie ACP Community Edition](#unexpected-failure) + * [MCP 설정 가이드](#unexpected-failure) diff --git a/src/content/ja/installation/container-environment-variables.mdx b/src/content/ja/installation/container-environment-variables.mdx index de4f0b8c..3b7a99a1 100644 --- a/src/content/ja/installation/container-environment-variables.mdx +++ b/src/content/ja/installation/container-environment-variables.mdx @@ -209,7 +209,7 @@ AWS_ACCOUNT_ID環境変数値はWeb ConsoleでCloud Providerを設定で、Cross 以下の図のようにAccount ID部分で使用されます。
-![image-20241031-062026.png](/installation/container-environment-variables/image-20241031-062026.png) +image-20241031-062026.png
diff --git a/src/content/ja/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx b/src/content/ja/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx index c4abe3eb..5fae0870 100644 --- a/src/content/ja/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx +++ b/src/content/ja/installation/container-environment-variables/optimizing-dbmaxconnectionsize.mdx @@ -125,7 +125,7 @@ QueryPie ServerはConnection Poolを利用してQueryPie MySQLに接続を確立 Web Consoleで、`[API] Could not open JPA EntityManager for transaction`というエラーメッセージに遭遇します。
-![[API] Could not open JPA EntityManager for transaction](/installation/container-environment-variables/optimizing-dbmaxconnectionsize/Screenshot-2025-04-24-at-9.38.20-PM.png) +[API] Could not open JPA EntityManager for transaction
[API] Could not open JPA EntityManager for transaction
diff --git a/src/content/ja/installation/container-environment-variables/querypieweburl.mdx b/src/content/ja/installation/container-environment-variables/querypieweburl.mdx index 2fea6c29..6f6ba603 100644 --- a/src/content/ja/installation/container-environment-variables/querypieweburl.mdx +++ b/src/content/ja/installation/container-environment-variables/querypieweburl.mdx @@ -16,7 +16,7 @@ QUERYPIE_WEB_URLはサービスアクセス、認証連携、データダウン **QueryPieバージョン10.2.8から該当環境変数は使用されません。GeneralメニューのWeb Base URLに置き換えられます。**
-![screenshot-20250312-112533.png](/installation/container-environment-variables/querypieweburl/screenshot-20250312-112533.png) +screenshot-20250312-112533.png
diff --git a/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx b/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx index 234910c8..1ae75c6a 100644 --- a/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx +++ b/src/content/ja/installation/installation/installation-guide-setupv2sh.mdx @@ -169,7 +169,7 @@ $ Licenseファイルはウェブコンソール画面で入力できます。
-![Enter the license in PEM format.](/installation/installation/installation-guide-setupv2sh/image-20250718-063723.png) +Enter the license in PEM format.
Enter the license in PEM format.
@@ -199,7 +199,7 @@ Web ConsoleにアクセスするためのQueryPieのURLアドレスです。
-![image-20250520-081112.png](/installation/installation/installation-guide-setupv2sh/image-20250520-081112.png) +image-20250520-081112.png
### 製品別設定 @@ -239,7 +239,7 @@ Proxy接続のためのアドレスをQueryPie Databaseに登録した後、Serv User Agentからログインを試みると、ウェブブラウザを通じて認証を進行した後、User Agentを使用できる状態になります。
-![image-20250520-082706.png](/installation/installation/installation-guide-setupv2sh/image-20250520-082706.png) +image-20250520-082706.png
#### KAC: Proxy接続アドレス設定 @@ -258,7 +258,7 @@ UPDATE querypie.k_proxy_setting SET host = 'https://'; ```
-![image-20250520-084243.png](/installation/installation/installation-guide-setupv2sh/image-20250520-084243.png) +image-20250520-084243.png
diff --git a/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx b/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx index dff3d9ff..0b2f106a 100644 --- a/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx +++ b/src/content/ja/installation/installation/installation-guide-simple-configuration.mdx @@ -314,7 +314,7 @@ Web ConsoleにアクセスするためのQueryPieのURLアドレスです。
-![image-20250520-081112.png](/installation/installation/installation-guide-simple-configuration/image-20250520-081112.png) +image-20250520-081112.png
### 製品別設定 @@ -354,7 +354,7 @@ Proxy接続のためのアドレスをQueryPie Databaseに登録した後、Serv User Agentからログインを試みると、ウェブブラウザを通じて認証を進行した後、User Agentを使用できる状態になります。
-![image-20250520-082706.png](/installation/installation/installation-guide-simple-configuration/image-20250520-082706.png) +image-20250520-082706.png
#### KAC: Proxy接続アドレス設定 @@ -373,7 +373,7 @@ UPDATE querypie.k_proxy_setting SET host = 'https://'; ```
-![image-20250520-084243.png](/installation/installation/installation-guide-simple-configuration/image-20250520-084243.png) +image-20250520-084243.png
#### WAC: Proxy接続アドレス設定 diff --git a/src/content/ja/installation/querypie-acp-community-edition.mdx b/src/content/ja/installation/querypie-acp-community-edition.mdx index 19c61429..2084185e 100644 --- a/src/content/ja/installation/querypie-acp-community-edition.mdx +++ b/src/content/ja/installation/querypie-acp-community-edition.mdx @@ -94,7 +94,7 @@ bash <(curl -s https://dl.querypie.com/setup.v2.sh) ⏱️ インストールは通常**7～10分**程度かかります。
-![インストールが開始された画面](/installation/querypie-acp-community-edition/image-20250718-063107.png) +インストールが開始された画面
インストールが開始された画面
@@ -102,7 +102,7 @@ bash <(curl -s https://dl.querypie.com/setup.v2.sh)
-![インストールが完了した画面](/installation/querypie-acp-community-edition/image-20250718-063140.png) +インストールが完了した画面
インストールが完了した画面
@@ -129,7 +129,7 @@ QueryPieがインストールされたLinuxサーバのIPアドレスはユー メールで受け取った`.crt`ファイルをアップロードするか、PEM形式のテキスト内容をコピーして貼り付けてください。
-![PEM形式ライセンス入力画面](/installation/querypie-acp-community-edition/image-20250718-063723.png) +PEM形式ライセンス入力画面
PEM形式ライセンス入力画面
@@ -154,7 +154,7 @@ PEM形式ライセンス入力画面 * Password: `querypie`
-![初期ログイン画面](/installation/querypie-acp-community-edition/image-20260107-080840.png) +初期ログイン画面
初期ログイン画面
@@ -163,7 +163,7 @@ PEM形式ライセンス入力画面 qp-adminアカウントでログイン後、基本パスワードを別のパスワードに変更します。
-![初期パスワード変更画面](/installation/querypie-acp-community-edition/image-20260107-080542.png) +初期パスワード変更画面
初期パスワード変更画面
@@ -175,7 +175,7 @@ qp-adminアカウントでログイン後、基本パスワードを別のパス 環境設定のために管理者マニュアルを参照してください：[管理者マニュアル](../administrator-manual)
管理者ページに移動するには、右上の`Go to Admin Page`ボタンをクリックします。
-![ログイン後に表示されるユーザーダッシュボード](/installation/querypie-acp-community-edition/image-20260107-081618.png) +ログイン後に表示されるユーザーダッシュボード
ログイン後に表示されるユーザーダッシュボード
@@ -208,7 +208,7 @@ docker compose --profile=app exec app readyz 正常に起動した場合、以下のような画面が出力されます。
-![正常に起動した場合](/installation/querypie-acp-community-edition/image-20260107-083457.png) +正常に起動した場合
正常に起動した場合
@@ -239,7 +239,7 @@ QueryPie Communityインストールおよび使用中に疑問点があれば[Q 以下の手順に従ってMCPで**QueryPie顧客センター**プリセットを設定すると、チャット画面で直接サポートを受けられます。
-![image-20250718-070933.png](/installation/querypie-acp-community-edition/image-20250718-070933.png) +image-20250718-070933.png
1. Integrationタブ → Install QueryPie Customer Centerクリック。 diff --git a/src/content/ja/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx b/src/content/ja/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx index d3cc4a9f..1303dc74 100644 --- a/src/content/ja/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx +++ b/src/content/ja/installation/querypie-acp-community-edition/mcp-configuration-guide.mdx @@ -56,7 +56,7 @@ claude mcp add querypie --transport http {QuerPie_URL}/api/mcp 例) `claude mcp add querypie --transport http https://querypie.example.com/api/mcp`
-![MCP server追加](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-091753.png) +MCP server追加
MCP server追加
@@ -67,28 +67,28 @@ MCP server追加 まず、`/mcp`を入力して、現在設定されているMCP Serverの状態を確認します。
-![image-20251211-092208.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092208.png) +image-20251211-092208.png
リストから`querypie`を選択します。 その後、`Authenticate`を選択します。
-![image-20251211-092454.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092454.png) +image-20251211-092454.png
ブラウザが開いたら、QueryPieログインページでログインします。 正常にログインすると、ブラウザに「Authentication Successful」メッセージが表示されます。
-![image-20251211-092741.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092741.png) +image-20251211-092741.png
Claude Codeでも「Authentication successful. Connect to querypie.」メッセージが表示されます。
-![image-20251211-092842.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-092842.png) +image-20251211-092842.png
@@ -97,7 +97,7 @@ Connect to querypie.」メッセージが表示されます。 claude codeを実行していない状態であれば`claude mcp list`コマンドでmcp接続を確認できます。
-![claude mcp listコマンド実行結果](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251214-232657.png) +claude mcp listコマンド実行結果
claude mcp listコマンド実行結果
@@ -106,7 +106,7 @@ claude mcp listコマンド実行結果 クエリを通じて作業を実行してみます。
-![クエリ例](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251214-232033.png) +クエリ例
クエリ例
@@ -116,7 +116,7 @@ claude mcp listコマンド実行結果 'yes'または'yes, and don't ask again for querypie -…'を選択します。
-![回答例](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251214-232144.png) +回答例
回答例
@@ -146,7 +146,7 @@ ______ OAuthをサポートするサーバーは自動的に検出されます。
-![image-20251211-102950.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-102950.png) +image-20251211-102950.png
##### 2. OAuthログインを実行します。 @@ -160,11 +160,11 @@ Gemini CLIで`/mcp auth`コマンドを使用して認証を進めます。 正常にログインすると、ブラウザに「Authentication Successful」メッセージが表示されます。
-![image-20251211-104053.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-104053.png) +image-20251211-104053.png
-![image-20251211-103846.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251211-103846.png) +image-20251211-103846.png
ブラウザが自動的に開かない場合は、上図のように画面上に表示されるアドレスをブラウザに貼り付けて進めることもできます。 @@ -197,7 +197,7 @@ ______ Cursor SettingsでMCPツールが正しく連携されているか確認します。
-![image-20251212-012243.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251212-012243.png) +image-20251212-012243.png
______ @@ -228,7 +228,7 @@ ______ Windsurf Agents画面でMCPツールが正しく連携されているか確認します。
-![image-20251212-012554.png](/installation/querypie-acp-community-edition/mcp-configuration-guide/image-20251212-012554.png) +image-20251212-012554.png
diff --git a/src/content/ja/installation/system-architecture-and-network-access-control.mdx b/src/content/ja/installation/system-architecture-and-network-access-control.mdx index f7978ba6..6ff6dd93 100644 --- a/src/content/ja/installation/system-architecture-and-network-access-control.mdx +++ b/src/content/ja/installation/system-architecture-and-network-access-control.mdx @@ -15,7 +15,7 @@ QueryPie Server、QueryPie User Agent、User PCのWeb Browser、そして利用 TLS証明書を適用したウェブサービス、高可用性のための多重化構成などは含まれません。
-![Overview of QueryPie System Architecture ](/installation/system-architecture-and-network-access-control/image-20251204-043839.png) +Overview of QueryPie System Architecture
Overview of QueryPie System Architecture
diff --git a/src/content/ja/overview.mdx b/src/content/ja/overview.mdx index 550d53d0..a183d3cd 100644 --- a/src/content/ja/overview.mdx +++ b/src/content/ja/overview.mdx @@ -13,7 +13,7 @@ QueryPie ACPはセキュリティ作業自動化、多様なプラットフォ 複雑に散らばっている資産と権限をQueryPie ACPを通じて一箇所で管理してみてください。
-![How QueryPie Access Control Platform Works](/overview/QueryPie-ACP-Overview.png) +How QueryPie Access Control Platform Works
How QueryPie Access Control Platform Works
diff --git a/src/content/ja/overview/proxy-management.mdx b/src/content/ja/overview/proxy-management.mdx index 3001e05b..49bb7372 100644 --- a/src/content/ja/overview/proxy-management.mdx +++ b/src/content/ja/overview/proxy-management.mdx @@ -14,7 +14,7 @@ QueryPieは、ユーザーのデータベースおよびシステムへのアク ### QueryPieプロキシの紹介
-![proxy-introduction.png](/overview/proxy-management/proxy-introduction.png) +proxy-introduction.png
* **セキュリティの強化**：プロキシ機能は、ユーザーとリソース間のセキュアな仲介役として機能し、不正アクセスおよび潜在的なセキュリティ侵害に対するセキュリティレイヤーを追加する役割を果たします。 @@ -26,7 +26,7 @@ QueryPieは、ユーザーのデータベースおよびシステムへのアク ### QueryPieプロキシの動作方式
-![proxy-operation-flow.png](/overview/proxy-management/proxy-operation-flow.png) +proxy-operation-flow.png
1. **Proxy設定**：管理者は、QueryPieのインターフェース内でリソースごとにプロキシ使用の有無を設定します。 diff --git a/src/content/ja/overview/proxy-management/enable-database-proxy.mdx b/src/content/ja/overview/proxy-management/enable-database-proxy.mdx index 7a272b89..5d82bc30 100644 --- a/src/content/ja/overview/proxy-management/enable-database-proxy.mdx +++ b/src/content/ja/overview/proxy-management/enable-database-proxy.mdx @@ -20,7 +20,7 @@ Web SQLエディターと合わせてProxy接続をサポートすることで アクセスを許可する接続でProxy使用の可否を活性化します。
-![Administrator > Databases > Connection Management > DB Connections > Connection Details > Proxy Usage](/overview/proxy-management/enable-database-proxy/image-20240725-070857.png) +Administrator > Databases > Connection Management > DB Connections > Connection Details > Proxy Usage
Administrator > Databases > Connection Management > DB Connections > Connection Details > Proxy Usage
@@ -47,7 +47,7 @@ Proxy Usageオプションを活性化すると、Proxyで接続できるPortが
-![Administrator > Databases > Connection Management > DB Connections > Proxy Management](/overview/proxy-management/enable-database-proxy/image-20240725-071030.png) +Administrator > Databases > Connection Management > DB Connections > Proxy Management
Administrator > Databases > Connection Management > DB Connections > Proxy Management
diff --git a/src/content/ja/overview/system-architecture-overview.mdx b/src/content/ja/overview/system-architecture-overview.mdx index d179460f..7776f395 100644 --- a/src/content/ja/overview/system-architecture-overview.mdx +++ b/src/content/ja/overview/system-architecture-overview.mdx @@ -23,7 +23,7 @@ QueryPieのバイナリパッケージはDockerイメージとして作成され ### 試用評価のための簡単な構成
-![Simple System Configuration for Evaluation](/overview/system-architecture-overview/screenshot-20240801-115045.png) +Simple System Configuration for Evaluation
Simple System Configuration for Evaluation
@@ -59,7 +59,7 @@ QueryPieは、https://querypie-poc.customer.com/のようなTLS証明書が適 ### 実使用のためのシステム構成の要約
-![Summary of System Architecture for Real Use](/overview/system-architecture-overview/screenshot-20240801-115343.png) +Summary of System Architecture for Real Use
Summary of System Architecture for Real Use
diff --git a/src/content/ja/release-notes/9120-91214/menu-improvement-guide-9120.mdx b/src/content/ja/release-notes/9120-91214/menu-improvement-guide-9120.mdx index 605fa5ec..f495509d 100644 --- a/src/content/ja/release-notes/9120-91214/menu-improvement-guide-9120.mdx +++ b/src/content/ja/release-notes/9120-91214/menu-improvement-guide-9120.mdx @@ -11,43 +11,43 @@ import { Callout } from 'nextra/components'
-![cover-page.png](/release-notes/9120-91214/menu-improvement-guide-9120/cover-page.png) +cover-page.png
-![1.png](/release-notes/9120-91214/menu-improvement-guide-9120/1.png) +1.png
-![2.png](/release-notes/9120-91214/menu-improvement-guide-9120/2.png) +2.png
-![3.png](/release-notes/9120-91214/menu-improvement-guide-9120/3.png) +3.png
-![4.png](/release-notes/9120-91214/menu-improvement-guide-9120/4.png) +4.png
-![5.png](/release-notes/9120-91214/menu-improvement-guide-9120/5.png) +5.png
-![6.png](/release-notes/9120-91214/menu-improvement-guide-9120/6.png) +6.png
-![7.png](/release-notes/9120-91214/menu-improvement-guide-9120/7.png) +7.png
-![8.png](/release-notes/9120-91214/menu-improvement-guide-9120/8.png) +8.png
-![9.png](/release-notes/9120-91214/menu-improvement-guide-9120/9.png) +9.png
diff --git a/src/content/ja/support/premium-support.mdx b/src/content/ja/support/premium-support.mdx index 6e5eda39..f602266f 100644 --- a/src/content/ja/support/premium-support.mdx +++ b/src/content/ja/support/premium-support.mdx @@ -13,7 +13,7 @@ Enterprise Editionのお客様には、専用のCustomer Portalを通じて迅 * QueryPie Customer Portal：[こちら](https://help.support.querypie.com/)
-![image-20240801-023748.png](/support/premium-support/image-20240801-023748.png) +image-20240801-023748.png
製品に関するお問い合わせやバグ報告などをチケットとして登録でき、チケットの進捗状況をリアルタイムで確認できます。 diff --git a/src/content/ja/user-manual/database-access-control.mdx b/src/content/ja/user-manual/database-access-control.mdx index 71920571..c9d04b0c 100644 --- a/src/content/ja/user-manual/database-access-control.mdx +++ b/src/content/ja/user-manual/database-access-control.mdx @@ -17,7 +17,7 @@ import { Callout } from 'nextra/components'
-![Host Level privilegeが割り当てられた場合接続画面](/user-manual/database-access-control/image-20251218-114957.png) +Host Level privilegeが割り当てられた場合接続画面
Host Level privilegeが割り当てられた場合接続画面
@@ -25,7 +25,7 @@ Host Level privilegeが割り当てられた場合接続画面
-![Schema Level privilegeが割り当てられた場合接続画面](/user-manual/database-access-control/image-20251218-114753.png) +Schema Level privilegeが割り当てられた場合接続画面
Schema Level privilegeが割り当てられた場合接続画面
diff --git a/src/content/ja/user-manual/database-access-control/connecting-to-custom-data-source.mdx b/src/content/ja/user-manual/database-access-control/connecting-to-custom-data-source.mdx index 87cce156..311c5679 100644 --- a/src/content/ja/user-manual/database-access-control/connecting-to-custom-data-source.mdx +++ b/src/content/ja/user-manual/database-access-control/connecting-to-custom-data-source.mdx @@ -11,14 +11,14 @@ import { Callout } from 'nextra/components' 1. ユーザー画面上部Workflowメニューに移動します。 2. 左上`Submit Request`ボタンクリック後DB Access Request項目を選択します。
- ![Screenshot-2025-03-06-at-1.19.24-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-1.19.24-PM.png) + Screenshot-2025-03-06-at-1.19.24-PM.png
3. Approval Ruleを状況に合わせて設定しTitleも作成します。 4. DB Connection目録でTypeが'Custom Data Source'の項目を選択します。 5. 他のベンダーと異なりPrivilegeを選択できないため"-"で表記されます。 6. Expiration DateとReason for Request項目も状況に合わせて設定および作成します。
- ![Screenshot-2025-03-06-at-1.22.28-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-1.22.28-PM.png) + Screenshot-2025-03-06-at-1.22.28-PM.png
7. 作成が完了したら下部`Submit`ボタンをクリックして申請を完了します。 8. 管理者の承認を受けたら左上Workflow > Sent Request > Doneメニューで確認できます。 @@ -36,13 +36,13 @@ import { Callout } from 'nextra/components' * QueryPie Agentを実行します。 * Database項目でCustom Data Sourceを確認できます。
- ![Screenshot-2025-03-06-at-2.05.26-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.05.26-PM.png) + Screenshot-2025-03-06-at-2.05.26-PM.png
2. **Connection Guide確認** * AgentでCustom Data Sourceコネクション行をクリックするとPort情報を含む行が見えます。 * 上記行を右クリックした後Connection Guideをクリックすると接続情報を確認できます。
- ![Screenshot-2025-03-06-at-2.08.11-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.08.11-PM.png) + Screenshot-2025-03-06-at-2.08.11-PM.png
* UID/PWは修正できないdb username、db passwordで表示されます。 * Privilegesは"-"で表示されます。 @@ -51,7 +51,7 @@ import { Callout } from 'nextra/components' * **HostとPortはConnection Guideに明記されている情報を入力する必要があります。** * ベンダーに応じて追加情報を入力します。
- ![Screenshot-2025-03-06-at-2.18.26-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.18.26-PM.png) + Screenshot-2025-03-06-at-2.18.26-PM.png
@@ -65,11 +65,11 @@ import { Callout } from 'nextra/components' * ユーザー画面上部Databasesをクリックします。 * 左側コネクション目録でQueryPie Connectionsをクリックするとアクセス権限があるCustom Data Sourceが表示されます。
- ![Screenshot-2025-03-06-at-2.22.22-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.22.22-PM.png) + Screenshot-2025-03-06-at-2.22.22-PM.png
2. **接続不可案内** * Custom Data Source選択時Connectボタンが非活性化されます。 * 下記のようなツールチップが表示されウェブでは接続が不可です。
"Access is only possible through a proxy and cannot be accessed through the web. Please open the QueryPie Agent to connect to the Custom Data Source."
- ![Screenshot-2025-03-06-at-2.23.37-PM.png](/user-manual/database-access-control/connecting-to-custom-data-source/Screenshot-2025-03-06-at-2.23.37-PM.png) + Screenshot-2025-03-06-at-2.23.37-PM.png
diff --git a/src/content/ja/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx b/src/content/ja/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx index e7181550..20c6db4a 100644 --- a/src/content/ja/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx +++ b/src/content/ja/user-manual/database-access-control/connecting-to-proxy-without-agent.mdx @@ -21,7 +21,7 @@ Redash、Tableau、ZepplinのようなウェブサービスでDBに接続しよ
-![QueryPie Web > Data Access Control > Databases > Proxy Info](/user-manual/database-access-control/connecting-to-proxy-without-agent/image-20240731-133408.png) +QueryPie Web > Data Access Control > Databases > Proxy Info
QueryPie Web > Data Access Control > Databases > Proxy Info
@@ -33,7 +33,7 @@ QueryPie Web > Data Access Control > Databases > Proxy Info 4. 下部の`Create Token`ボタンをクリックしてユーザー認証トークンを発行します。
-![QueryPie Web > Data Access Control > Databases > Proxy Info > Create Token](/user-manual/database-access-control/connecting-to-proxy-without-agent/image-20240731-133805.png) +QueryPie Web > Data Access Control > Databases > Proxy Info > Create Token
QueryPie Web > Data Access Control > Databases > Proxy Info > Create Token
diff --git a/src/content/ja/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx b/src/content/ja/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx index 075e2a79..13c9dcb7 100644 --- a/src/content/ja/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx +++ b/src/content/ja/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication.mdx @@ -14,25 +14,25 @@ QueryPie管理者がBigQueryコネクション認証方式をOAuth 2.0に設定 1. QueryPieユーザーページのDatabase項目下のコネクションリストでBigQueryコネクションを選択します。
(管理者からアクセスが許可されなければコネクションリストで見ることができません.)
- ![ユーザーページDatabaseのコネクションリストで見えるBigQueryコネクション](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250226-020846.png) + ユーザーページBigQueryコネクションのReset Tokenボタン
ユーザーページDatabaseのコネクションリストで見えるBigQueryコネクション
2. `Connect`ボタンを押すと表示されるポップアップでログインに使用するGoogleアカウントを選択します。
- ![image-20250123-110105.png](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250123-110105.png) + image-20250123-110105.png
3. サービスにログインすることについての案内画面で「続行」を選択します。
- ![サービスにログイン](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250123-110419.png) + サービスにログイン
サービスにログイン
4. Googleアカウントへのアクセスを許可します。
- ![image-20250123-111820.png](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250123-111820.png) + image-20250123-111820.png
5. しばらく待つと接続が完了します。 @@ -50,7 +50,7 @@ refresh tokenにも期限がある場合があり、様々な原因によって このボタンをクリックするとクライアントに保存された既存トークンが削除され、OAuth認証の最初（Googleアカウントのサービスにログイン）から再び進行できます。
-![ユーザーページBigQueryコネクションのReset Tokenボタン](/user-manual/database-access-control/connecting-via-google-bigquery-oauth-authentication/image-20250226-020846.png) +ユーザーページBigQueryコネクションのReset Tokenボタン
ユーザーページBigQueryコネクションのReset Tokenボタン
diff --git a/src/content/ja/user-manual/database-access-control/connecting-with-web-sql-editor.mdx b/src/content/ja/user-manual/database-access-control/connecting-with-web-sql-editor.mdx index b3653a0a..ae30ade9 100644 --- a/src/content/ja/user-manual/database-access-control/connecting-with-web-sql-editor.mdx +++ b/src/content/ja/user-manual/database-access-control/connecting-with-web-sql-editor.mdx @@ -16,7 +16,7 @@ QueryPieではウェブブラウザを通じてクエリを実行し、データ 個別ユーザーまたはグループにアクセス権限が付与されたデータベースコネクションリストを確認でき、作業を実行するコネクションを選択してデータベースに接続できます。
-![User > Databasesのコネクション選択および接続画面](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20251218-115500.png) +User > Databasesのコネクション選択および接続画面
User > Databasesのコネクション選択および接続画面
@@ -36,7 +36,7 @@ User > Databasesのコネクション選択および接続画面 #### 1. 左上オブジェクトパネル
-![SQL Editor > Connection Panel](/user-manual/database-access-control/connecting-with-web-sql-editor/screenshot-20240802-141439.png) +SQL Editor > Connection Panel
SQL Editor > Connection Panel
@@ -49,7 +49,7 @@ SQL Editor > Connection Panel #### 2. 左側オブジェクトパネル
-![SQL Editor > Connection Panel](/user-manual/database-access-control/connecting-with-web-sql-editor/screenshot-20240802-141927.png) +SQL Editor > Connection Panel
SQL Editor > Connection Panel
@@ -64,7 +64,7 @@ SQL Editor > Connection Panel #### 3. 上部ツールバー
-![QueryPie Web > Database Access Control > SQL Editor > Toolbar](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240731-115955.png) +QueryPie Web > Database Access Control > SQL Editor > Toolbar
QueryPie Web > Database Access Control > SQL Editor > Toolbar
@@ -89,7 +89,7 @@ QueryPie Web > Database Access Control > SQL Editor > Toolbar
-![SQL Editor > Editor Tab & Result](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-052240.png) +SQL Editor > Editor Tab & Result
SQL Editor > Editor Tab & Result
@@ -103,7 +103,7 @@ SQL Editor > Editor Tab & Result #### 3. Queriesパネル
-![SQL Editor > Queries Panel ](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-052539.png) +SQL Editor > Queries Panel
SQL Editor > Queries Panel
@@ -119,7 +119,7 @@ SQL Editor > Queries Panel #### 4. Object Infoパネル
-![SQL Editor > Object Info Panel ](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-053427.png) +SQL Editor > Object Info Panel
SQL Editor > Object Info Panel
@@ -136,7 +136,7 @@ SQL Editor > Object Info Panel #### 5. SQL Historyパネル
-![SQL Editor > SQL History Panel](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20240802-054007.png) +SQL Editor > SQL History Panel
SQL Editor > SQL History Panel
@@ -170,7 +170,7 @@ Ledger政策または接続政策によってクエリを実行時理由入力 総300文字まで入力可能です。
-![image-20241031-233232.png](/user-manual/database-access-control/connecting-with-web-sql-editor/image-20241031-233232.png) +image-20241031-233232.png
diff --git a/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx b/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx index 6e6ab50d..f625f909 100644 --- a/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx +++ b/src/content/ja/user-manual/database-access-control/setting-default-privilege.mdx @@ -14,7 +14,7 @@ import { Callout } from 'nextra/components' ### Default Privilege設定
-![QueryPie Web > Database Access Control > Databases > Privileges](/user-manual/database-access-control/setting-default-privilege/image-20240731-124310.png) +QueryPie Web > Database Access Control > Databases > Privileges
QueryPie Web > Database Access Control > Databases > Privileges
@@ -24,7 +24,7 @@ QueryPie Web > Database Access Control > Databases > Privileges 2. 付与された権限が2個以上の場合、ユーザーは別途Default Privilege設定をする必要があります。
-![QueryPie Web > Database Access Control > Databases > Privileges > Default Privilege Setting](/user-manual/database-access-control/setting-default-privilege/image-20240731-124808.png) +QueryPie Web > Database Access Control > Databases > Privileges > Default Privilege Setting
QueryPie Web > Database Access Control > Databases > Privileges > Default Privilege Setting
diff --git a/src/content/ja/user-manual/kubernetes-access-control.mdx b/src/content/ja/user-manual/kubernetes-access-control.mdx index 0abe5488..3f6c45e4 100644 --- a/src/content/ja/user-manual/kubernetes-access-control.mdx +++ b/src/content/ja/user-manual/kubernetes-access-control.mdx @@ -10,7 +10,7 @@ QueryPieはKubernetesクラスターに対するアクセス権限を制御し クエリパイエージェントを通じて権限を付与されたクラスターに接続でき、クラスター接続に必要なKUBECONFIGファイルはエージェントを通じて構成されます。
-![QueryPie Web > Kubernetes Access Control > Kubernetes](/user-manual/kubernetes-access-control/image-20240724-050502.png) +QueryPie Web > Kubernetes Access Control > Kubernetes
QueryPie Web > Kubernetes Access Control > Kubernetes
diff --git a/src/content/ja/user-manual/kubernetes-access-control/checking-access-permission-list.mdx b/src/content/ja/user-manual/kubernetes-access-control/checking-access-permission-list.mdx index ebb8bc47..ed51bbf6 100644 --- a/src/content/ja/user-manual/kubernetes-access-control/checking-access-permission-list.mdx +++ b/src/content/ja/user-manual/kubernetes-access-control/checking-access-permission-list.mdx @@ -15,14 +15,14 @@ import { Callout } from 'nextra/components' ユーザーはQueryPieログイン後、Kubernetesメニューで自分に付与された権限を照会できます。
-![QueryPie Web > Kubernetes Access Control > Kuber > Select a Role](/user-manual/kubernetes-access-control/checking-access-permission-list/image-20240721-081220.png) +QueryPie Web > Kubernetes Access Control > Kuber > Select a Role
QueryPie Web > Kubernetes Access Control > Kuber > Select a Role
-![QueryPie Web > System Access Control > Kubernetes > Select a Role](/user-manual/kubernetes-access-control/checking-access-permission-list/image-20240723-155143.png) +QueryPie Web > System Access Control > Kubernetes > Select a Role
QueryPie Web > System Access Control > Kubernetes > Select a Role
@@ -36,7 +36,7 @@ QueryPie Web > System Access Control > Kubernetes > Select a Role ### アクセス権限リストの確認
-![QueryPie Web > System Access Control > Kubernetes ](/user-manual/kubernetes-access-control/checking-access-permission-list/image-20240721-081324.png) +QueryPie Web > System Access Control > Kubernetes
QueryPie Web > System Access Control > Kubernetes
diff --git a/src/content/ja/user-manual/multi-agent.mdx b/src/content/ja/user-manual/multi-agent.mdx index 14fa6404..4a2297fb 100644 --- a/src/content/ja/user-manual/multi-agent.mdx +++ b/src/content/ja/user-manual/multi-agent.mdx @@ -38,35 +38,35 @@ QueryPie Hostバージョンが`10.2.8`以上バージョンの場合サポー 1. QueryPieログイン後右上プロフィールをクリックした後Download & Support > `Multi-Agent`ボタンをクリックします。
- ![QueryPie Web > プロフィールメニュー](/user-manual/multi-agent/screenshot-20250217-110358.png) + QueryPie Web > プロフィールメニュー
QueryPie Web > プロフィールメニュー
2. QueryPie Multi-Agent Downloadsポップアップウィンドウが実行されるとStep 1で使用中のPCオペレーティングシステムに合うインストールファイルをダウンロードした後Step 3にあるQueryPie URLをコピーしておきます。

- ![QueryPie Web > QueryPie Multi-Agent Download](/user-manual/multi-agent/screenshot-20250413-233322.png) + QueryPie Web > QueryPie Multi-Agent Download
QueryPie Web > QueryPie Multi-Agent Download
3. ダウンロードしたQueryPie Multi-Agentインストールプログラムを実行した後.appファイルをApplicationsフォルダにコピーしてインストールを完了します。
- ![Mac OSインストールプログラム](/user-manual/multi-agent/screenshot-20250217-105557.png) + Mac OSインストールプログラム
Mac OSインストールプログラム
4. インストール完了されたQueryPie Agentを実行するとHost初回登録ページが開きます。
QueryPie Host入力欄に事前にコピーしておいたQueryPie URLを入力して`Next`ボタンをクリックするとログイン画面にアクセスします。
- ![Multi-Agent > Host Setting](/user-manual/multi-agent/screenshot-20250217-105917.png) + Multi-Agent > Host Setting
Multi-Agent > Host Setting
5. 入力したホストのログインページで認証情報を入力してContinueボタンをクリックします。
- ![Multi-Agent > ログイン](/user-manual/multi-agent/screenshot-20250217-110106.png) + Multi-Agent > ログイン
Multi-Agent > ログイン
@@ -78,14 +78,14 @@ QueryPie Hostバージョンが`10.2.8`以上バージョンの場合サポー 1. Databaseタブで選択されたQueryPie Hostに対して権限が付与されておりProxy使用が可能なDatabase Connection目録を確認できます。
- ![Multi-Agent > Databases](/user-manual/multi-agent/screenshot-20250307-105512.png) + Multi-Agent > Databases
Multi-Agent > Databases
2. 接続したいコネクションを選択してマウス右ボタンをクリックするとコンテキストメニューが開きます。
- ![Multi-Agent > Databases > Context-menu](/user-manual/multi-agent/screenshot-20250307-105433.png) + Multi-Agent > Databases > Context-menu
Multi-Agent > Databases > Context-menu
@@ -107,7 +107,7 @@ Open Connection With、Copy as JDBC URL機能は10.2.6またはその以降バ Settings > Databasesで3rd Partyツール関連設定を管理できます。
-![Multi-Agent > Settings > Databases](/user-manual/multi-agent/screenshot-20250413-235252.png) +Multi-Agent > Settings > Databases
Multi-Agent > Settings > Databases
@@ -131,28 +131,28 @@ Multi-Agent > Settings > Databases 多重privilegeを付与された後ユーザーが特定privilegeをdefaultに設定しないと接続できないためもしdefault privilegeが設定されていない場合は下記図のような警告アイコンが表示されます。
-![image-20250513-025002.png](/user-manual/multi-agent/image-20250513-025002.png) +image-20250513-025002.png
1. 多重Privilegeが割り当てられたコネクションに対してマウス右ボタンを押してメニューを呼び出します。 2. メニューでConnection Informationを選択します。
- ![Connection Information](/user-manual/multi-agent/image-20250513-042753.png) + Connection Information
Connection Information
3. Original InformationのPrivilegeで編集(鉛筆形アイコン)ボタンをクリックします。


- ![image-20250513-043056.png](/user-manual/multi-agent/image-20250513-043056.png) + image-20250513-043056.png
4. Previlege Nameの項目中一つを選択して保存します。
- ![image-20250513-044616.png](/user-manual/multi-agent/image-20250513-044616.png) + image-20250513-044616.png
5. 警告アイコンが消え割り当てられたprivilege名前が該当コネクションに見えるか確認します。


- ![image-20250513-045054.png](/user-manual/multi-agent/image-20250513-045054.png) + image-20250513-045054.png
### KAC @@ -162,7 +162,7 @@ Multi-Agent > Settings > Databases Roleセレクターで本人に付与されたRole中一つを選択すると、選択されたRoleに権限が付与されているK8s Cluster目録を確認できます。
-![Multi-Agent > Kubernetes](/user-manual/multi-agent/screenshot-20250217-113908.png) +Multi-Agent > Kubernetes
Multi-Agent > Kubernetes
@@ -177,7 +177,7 @@ Proxyを通じてkubectlコマンドを使用するには**初回1回のKubeconf その後使用するターミナルでコピーしたコマンドを貼り付けて実行します。
-![Multi-Agent > Setting > Kubernetes](/user-manual/multi-agent/screenshot-20250217-113712.png) +Multi-Agent > Setting > Kubernetes
Multi-Agent > Setting > Kubernetes
@@ -189,14 +189,14 @@ Multi-Agent > Setting > Kubernetes 1. RoleドロップダウンでRoleを選択すると、選択したRoleでアクセスできるサーバー目録を確認できます。
- ![Multi-Agent > Servers](/user-manual/multi-agent/screenshot-20250413-234048.png) + Multi-Agent > Servers
Multi-Agent > Servers
2. サーバーを選択して右クリックしてコンテキストメニューを開き、Open Connection With > ターミナルToolを選択します。
- ![Multi-Agent > Servers](/user-manual/multi-agent/screenshot-20250413-234314.png) + Multi-Agent > Servers
Multi-Agent > Servers
@@ -206,7 +206,7 @@ Multi-Agent > Setting > Kubernetes 1. ただし、Server AgentがないWindows Serverに接続時、Custom Accountのみ選択でき、Custom Account入力フィールドとPassword入力フィールドは表記されません。Server AgentがあるWindows Serverでは使用できません。 4. 選択したターミナルツールでサーバーに接続できます。
- ![screenshot-20250413-234644.png](/user-manual/multi-agent/screenshot-20250413-234644.png) + screenshot-20250413-234644.png
@@ -229,19 +229,19 @@ Multi-Agent > Setting > Kubernetes 1. `Servers`タブで権限を要求するサーバーを選択してマウス右ボタンをクリックしてコンテキストメニューを開きます。

- ![Screenshot-2025-07-22-at-11.12.13-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.13-AM.png) + Screenshot-2025-07-22-at-11.12.13-AM.png
2. `Open Connection With`で使用したいターミナルツールを選択します。


- ![Screenshot-2025-07-22-at-11.12.16-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.16-AM.png) + Screenshot-2025-07-22-at-11.12.16-AM.png
3. アカウント選択窓が現れると下部にある`Request Server Privilege`ボタンをクリックします。


- ![Screenshot-2025-07-22-at-11.12.33-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.33-AM.png) + Screenshot-2025-07-22-at-11.12.33-AM.png
* このボタンをクリックするとQueryPieウェブページの権限要求画面に移動し、以前に選択したRole、サーバーグループ、サーバー、アカウント情報が自動で入力されています。

- ![Screenshot-2025-07-22-at-11.12.49-AM.png](/user-manual/multi-agent/Screenshot-2025-07-22-at-11.12.49-AM.png) + Screenshot-2025-07-22-at-11.12.49-AM.png
@@ -253,7 +253,7 @@ Multi-Agent > Setting > Kubernetes #### エージェントサーバー目録照会時使用可能なフィルター
-![Multi-Agent > Servers](/user-manual/multi-agent/Screenshot-2025-08-25-at-4.57.03-PM.png) +Multi-Agent > Servers
Multi-Agent > Servers
@@ -267,7 +267,7 @@ Multi-Agent > Servers Setting > Serversでターミナルツール関連設定を管理できます。
-![Multi-Agent > Setting > Servers](/user-manual/multi-agent/screenshot-20250413-235301.png) +Multi-Agent > Setting > Servers
Multi-Agent > Setting > Servers
@@ -283,7 +283,7 @@ Multi-Agent > Setting > Servers 1. Settings > Hostsで`+ Add New Host`ボタンをクリックした後新しいHostのドメインを入力して保存します。
- ![Multi-Agent > Setting > General > Add New Host](/user-manual/multi-agent/screenshot-20250413-235030.png) + Multi-Agent > Setting > General > Add New Host
Multi-Agent > Setting > General > Add New Host
@@ -291,14 +291,14 @@ Multi-Agent > Setting > Servers 2. 新しいHost登録が成功した場合Toastで案内されます。目録で新しいHostが追加されたことを確認し、右上の`X`ボタンを押して設定ページを出ます。 1. Host目録で希望するHostをクリックしてすぐに転換できます。
- ![Multi-Agent > Setting > General](/user-manual/multi-agent/screenshot-20250413-235051.png) + Multi-Agent > Setting > General
Multi-Agent > Setting > General
3. プロフィールボタンをクリックすると登録されたHost目録を確認できます。クリックしてHost間転換が可能です。
- ![Multi-Agent > プロフィールメニュー選択](/user-manual/multi-agent/screenshot-20250217-114200.png) + Multi-Agent > プロフィールメニュー選択
Multi-Agent > プロフィールメニュー選択
@@ -312,13 +312,13 @@ Host転換はログイン時には必須ですが、ログイン後Proxy接続 1. システムトレイまたはメニューバーでMulti Agentアイコン(または項目)をクリックした後、表示されるメニューで'Reset All Settings'を選択します。
-![ Status Bar Item (MacOS)](/user-manual/multi-agent/screenshot-20250414-000719.png) + Status Bar Item (MacOS)
Status Bar Item (MacOS)
-![Application Menu (MacOS)](/user-manual/multi-agent/screenshot-20250414-001207.png) +Application Menu (MacOS)
Application Menu (MacOS)
@@ -326,21 +326,21 @@ Application Menu (MacOS) 1. またはエージェント右上の歯車ボタンをクリックして設定ページにアクセスし、Hostsタブ下部のReset All Settingsボタンをクリックします。
- ![Multi-Agent > Setting > Hosts](/user-manual/multi-agent/screenshot-20250217-114241.png) + Multi-Agent > Setting > Hosts
Multi-Agent > Setting > Hosts
2. 確認モーダルでResetボタンをクリックするとローカルフォルダに保存されたすべての設定が初期化されます。
- ![Multi-Agent > Setting > Hosts > Reset All Settings](/user-manual/multi-agent/screenshot-20250217-114245.png) + Multi-Agent > Setting > Hosts > Reset All Settings
Multi-Agent > Setting > Hosts > Reset All Settings
3. Multi Agent初回設定(初回Host登録)ページにアクセスします。
- ![Multi-Agent > Host Setting](/user-manual/multi-agent/screenshot-20250217-114250.png) + Multi-Agent > Host Setting
Multi-Agent > Host Setting
@@ -353,13 +353,13 @@ Multi-agent使用中問題発生時次の手順に従ってログを抽出して #### GUI
-![MacOS](/user-manual/multi-agent/diagnostic-tools-for-macos.png) +MacOS
MacOS
-![Windows](/user-manual/multi-agent/diagnostic-tools-for-windows.png) +Windows
Windows
diff --git a/src/content/ja/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx b/src/content/ja/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx index 4a035f0f..b9e43432 100644 --- a/src/content/ja/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx +++ b/src/content/ja/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide.mdx @@ -68,11 +68,11 @@ appindicatorsupport@rgcjonas.gmail.com [https://extensions.gnome.org/extension/615/appindicator-support/](https://extensions.gnome.org/extension/615/appindicator-support/)
-![Screenshot-20250404-144620.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/Screenshot-20250404-144620.png) +Screenshot-20250404-144620.png
-![image-20250404-054650.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250404-054650.png) +image-20250404-054650.png
### Debianベース @@ -190,17 +190,17 @@ GNOMEデスクトップ環境では、ユーザーのパスワード、暗号化 Passwords and Keysアプリで**Loginストレージがロックされていると**マルチエージェント実行時に管理者権限を要求します。
-![image-20250403-080719.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250403-080719.png) +image-20250403-080719.png
-![image-20250403-080458.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250403-080458.png) +image-20250403-080458.png
Unlockボタンでロックを解除しておくと実行段階で管理者権限を要求しません。
-![image-20250403-080814.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250403-080814.png) +image-20250403-080814.png
## Troubleshooting @@ -211,7 +211,7 @@ Default Browserを設定しないとリンクが開きません。 ブラウザ内の設定でデフォルトブラウザを設定してください。
-![image-20250404-100924.png](/user-manual/multi-agent/multi-agent-linux-installation-and-usage-guide/image-20250404-100924.png) +image-20250404-100924.png
diff --git a/src/content/ja/user-manual/my-dashboard.mdx b/src/content/ja/user-manual/my-dashboard.mdx index af9dbd66..cc51dd05 100644 --- a/src/content/ja/user-manual/my-dashboard.mdx +++ b/src/content/ja/user-manual/my-dashboard.mdx @@ -20,7 +20,7 @@ QueryPie Webログインが成功するとユーザーダッシュボード画
-![QueryPieログイン画面](/user-manual/my-dashboard/image-20250725-085352.png) +QueryPieログイン画面
QueryPieログイン画面
@@ -38,7 +38,7 @@ QueryPieログイン画面 個人情報処理指針(Privacy Policy)リンクを通じてクエリパイのユーザー個人情報に対する取扱いポリシーを確認できます。
-![クッキー設定画面](/user-manual/my-dashboard/image-20250724-094214.png) +クッキー設定画面
クッキー設定画面
@@ -58,14 +58,14 @@ QueryPie 10.2.2基準提供される2次認証手段はGoogle OTP、Email二つ * ログインページでログインパスワードを入力します。 * 初回ログイン時ポップアップウィンドウに出力されるQR Codeを使用してAuthenticatorアプリに登録します。画面に'Google Authenticator、Microsoft Authenticator、Okta Verifyなどのような認証アプリをダウンロードしてください'という案内文句が表示され、App StoreまたはGoogle Play Storeで互換性のある認証アプリを簡単に選択してインストールできます。
- ![Authenticatorアプリ登録用QR code](/user-manual/my-dashboard/image-20250808-063052-(2).png) + Authenticator 앱 등록용 QR code
Authenticatorアプリ登録用QR code
* Authenticatorアプリで出力する1回用認証コードを入力します。
- ![1回用認証コード入力](/user-manual/my-dashboard/image-20241220-021546.png) + 1回用認証コード入力
1回用認証コード入力
@@ -75,7 +75,7 @@ QueryPie 10.2.2基準提供される2次認証手段はGoogle OTP、Email二つ * 本人メールの受信トレイで受信した認証メールの認証コードを確認します。
認証コードは30分間有効です。 * "Resend authentication code"を通じて認証メールの再送信を要求できます。2回目の再送信要求は5分後に可能です。
- ![1回用認証コード入力 (Email)](/user-manual/my-dashboard/image-20241220-021636.png) + 1回用認証コード入力 (Email)
1回用認証コード入力 (Email)
@@ -88,7 +88,7 @@ QueryPie 10.2.2基準提供される2次認証手段はGoogle OTP、Email二つ ダッシュボードでは現在ログインしたユーザーに付与された役割権限、所属グループなどの基本情報および決裁現況、最近接続したコネクション目録などを一目で確認できます。
-![My Dashboard](/user-manual/my-dashboard/screenshot-20240801-142503.png) +My Dashboard
My Dashboard
@@ -121,7 +121,7 @@ QueryPie管理者役割を割り当てられたユーザーに限り上部メニ 該当ボタンを押すと管理者ページが別途タブで開きます。
-![My Dashboard > 右上メニュー](/user-manual/my-dashboard/screenshot-20240801-145006.png) +My Dashboard > 右上メニュー
My Dashboard > 右上メニュー
diff --git a/src/content/ja/user-manual/my-dashboard/user-password-reset-via-email.mdx b/src/content/ja/user-manual/my-dashboard/user-password-reset-via-email.mdx index 8bd5f6e5..8e0ae030 100644 --- a/src/content/ja/user-manual/my-dashboard/user-password-reset-via-email.mdx +++ b/src/content/ja/user-manual/my-dashboard/user-password-reset-via-email.mdx @@ -24,7 +24,7 @@ ID ProviderやLDAPのように認証情報がQueryPie外部にある場合、こ ユーザーが受信するメールの内容は以下のようなものです。
-![パスワードリセットメール](/user-manual/my-dashboard/user-password-reset-via-email/image-20241218-224655.png) +パスワードリセットメール
パスワードリセットメール
@@ -37,41 +37,41 @@ ID ProviderやLDAPのように認証情報がQueryPie外部にある場合、こ 1. ログインページの「Forgot your password?」リンクをクリックします。
- ![Forgot your password?](/user-manual/my-dashboard/user-password-reset-via-email/image-20241218-233331.png) + Forgot your password?
Forgot your password?
2. ダイアログで自分のIDを入力し`Request`ボタンをクリックします。

- ![パスワードリセット要求](/user-manual/my-dashboard/user-password-reset-via-email/image-20241220-030541.png) + パスワードリセット要求
パスワードリセット要求
3. 自分のメールの受信トレイで本人確認のための認証コードが受信されているか確認します。

- ![メールで受信した認証コード](/user-manual/my-dashboard/user-password-reset-via-email/image-20241218-234314.png) + メールで受信した認証コード
メールで受信した認証コード
4. メールで確認した認証コードを入力します。受信した認証コードは30分以内に入力する必要があります。メールを受信できなかった場合は「Resend authentication code」リンクを押して認証コードメールを再要求できます。ただし、再送信要求は最初の再送信後5分経過してから可能です。

- ![認証コード入力](/user-manual/my-dashboard/user-password-reset-via-email/image-20241220-030233.png) + 認証コード入力
認証コード入力
5. 自分のIDを入力し新しいパスワードを登録します。


- ![新しいパスワード入力](/user-manual/my-dashboard/user-password-reset-via-email/image-20241219-002622.png) + 新しいパスワード入力
新しいパスワード入力
- ![パスワード変更確認](/user-manual/my-dashboard/user-password-reset-via-email/image-20241219-000927.png) + パスワード変更確認
パスワード変更確認
diff --git a/src/content/ja/user-manual/preferences.mdx b/src/content/ja/user-manual/preferences.mdx index 1fe16d62..0154a191 100644 --- a/src/content/ja/user-manual/preferences.mdx +++ b/src/content/ja/user-manual/preferences.mdx @@ -15,7 +15,7 @@ Preference画面を通じてQueryPieユーザーの個人別環境を設定で 個別ユーザーの環境設定を行うには、上部メニューバー右側のユーザーアカウントをクリックし、メニューからPreferencesボタンをクリックします。
-![image-20250724-092314.png](/user-manual/preferences/image-20250724-092314.png) +image-20250724-092314.png
@@ -29,7 +29,7 @@ SSO Login使用時は、パスワード変更はQueryPieではなく個別IdPの
-![上部メニューバー > Profile > Preferences > My Account](/user-manual/preferences/image-20250725-050431.png) +上部メニューバー > Profile > Preferences > My Account
上部メニューバー > Profile > Preferences > My Account
@@ -56,7 +56,7 @@ Approval Settingsタブでは代理決裁を設定できます。
-![上部メニューバー > Profile > Preferences > Approver Settings](/user-manual/preferences/image-20250725-050830.png) +上部メニューバー > Profile > Preferences > Approver Settings
上部メニューバー > Profile > Preferences > Approver Settings
@@ -73,7 +73,7 @@ Approval Settingsタブでは代理決裁を設定できます。 EditorタブではSQLエディターの表示方式および機能を設定します。
-![上部メニューバー > Profile > Preferences > Editor](/user-manual/preferences/image-20250725-051417.png) +上部メニューバー > Profile > Preferences > Editor
上部メニューバー > Profile > Preferences > Editor
@@ -98,7 +98,7 @@ EditorタブではSQLエディターの表示方式および機能を設定し ShortcutタブではSQL Editorに適用されるショートカットキーを照会し、ダブルクリックして修正できます。
-![上部メニューバー > Profile > Preferences > Shortcut](/user-manual/preferences/image-20250725-052245.png) +上部メニューバー > Profile > Preferences > Shortcut
上部メニューバー > Profile > Preferences > Shortcut
@@ -110,7 +110,7 @@ ShortcutタブではSQL Editorに適用されるショートカットキーを ConfigurationタブではKerberosキータブを管理できます。`Create Keatab`を押してキータブファイルをアップロードしてください。
-![上部メニューバー > Profile > Preferences > Configuration](/user-manual/preferences/image-20250725-052630.png) +上部メニューバー > Profile > Preferences > Configuration
上部メニューバー > Profile > Preferences > Configuration
@@ -122,7 +122,7 @@ ConfigurationタブではKerberosキータブを管理できます。`Create Kea TerminalタブではSSHなどテキストベース接続に表示されるユーザーページのフォントサイズ（基本12、最小9、最大24）とカラーテーマを指定できます。
-![上部メニューバー > Profile > Preferences > Terminal](/user-manual/preferences/image-20250725-053323.png) +上部メニューバー > Profile > Preferences > Terminal
上部メニューバー > Profile > Preferences > Terminal
@@ -136,7 +136,7 @@ TerminalタブではSSHなどテキストベース接続に表示されるユー 個人情報処理指針はインターネットのQueryPieホームページにアクセス可能な状態でのみ見ることができます。
[https://www.querypie.com/privacy-policy](https://www.querypie.com/privacy-policy) (英語)
[https://www.querypie.com/ko/privacy-policy](https://www.querypie.com/ko/privacy-policy) (韓国語)
[https://www.querypie.com/ja/privacy-policy](https://www.querypie.com/ja/privacy-policy) (日本語)
-![上部メニューバー > Profile > Preferences > Terminal](/user-manual/preferences/image-20250725-053955.png) +上部メニューバー > Profile > Preferences > Terminal
上部メニューバー > Profile > Preferences > Terminal
@@ -152,7 +152,7 @@ QueryPie Labタブでは実験室機能を提供し、ダークモード、高
-![上部メニューバー > Profile > Preferences > QueryPie Lab](/user-manual/preferences/image-20250725-054439.png) +上部メニューバー > Profile > Preferences > QueryPie Lab
上部メニューバー > Profile > Preferences > QueryPie Lab
diff --git a/src/content/ja/user-manual/server-access-control.mdx b/src/content/ja/user-manual/server-access-control.mdx index 5763fadb..1edafa22 100644 --- a/src/content/ja/user-manual/server-access-control.mdx +++ b/src/content/ja/user-manual/server-access-control.mdx @@ -11,7 +11,7 @@ QueryPieでは制御された環境で接続権限があるサーバーに対し 接続権限は個別ユーザーに付与されることもあり、ユーザーグループに付与されることもあります。
-![QueryPie Web > Server Access Control > Servers](/user-manual/server-access-control/image-20240724-050800.png) +QueryPie Web > Server Access Control > Servers
QueryPie Web > Server Access Control > Servers
diff --git a/src/content/ja/user-manual/server-access-control/connecting-to-authorized-servers.mdx b/src/content/ja/user-manual/server-access-control/connecting-to-authorized-servers.mdx index 4f4a9593..9c258791 100644 --- a/src/content/ja/user-manual/server-access-control/connecting-to-authorized-servers.mdx +++ b/src/content/ja/user-manual/server-access-control/connecting-to-authorized-servers.mdx @@ -15,7 +15,7 @@ import { Callout } from 'nextra/components' ### Role選択
-![QueryPie Web > System Access Control > Servers > Select a Role](/user-manual/server-access-control/connecting-to-authorized-servers/image-20240723-155143.png) +QueryPie Web > System Access Control > Servers > Select a Role
QueryPie Web > System Access Control > Servers > Select a Role
@@ -28,7 +28,7 @@ QueryPie Web > System Access Control > Servers > Select a Role ### サーバーに接続
-![QueryPie Web > System Access Control > Servers](/user-manual/server-access-control/connecting-to-authorized-servers/Screenshot-2025-08-25-at-4.46.51-PM.png) +QueryPie Web > System Access Control > Servers
QueryPie Web > System Access Control > Servers
@@ -73,7 +73,7 @@ QueryPie Agent (User Agent / Multi-Agent)インストール後、権限を付与 11.3.0からMulti-AgentでCustom Accountを選択してアカウントのパスワードを手動で入力して接続できるよう変更されました。
-![image-20251010-095324.png](/user-manual/server-access-control/connecting-to-authorized-servers/image-20251010-095324.png) +image-20251010-095324.png
diff --git a/src/content/ja/user-manual/server-access-control/using-web-sftp.mdx b/src/content/ja/user-manual/server-access-control/using-web-sftp.mdx index 8beb6439..f85c72e1 100644 --- a/src/content/ja/user-manual/server-access-control/using-web-sftp.mdx +++ b/src/content/ja/user-manual/server-access-control/using-web-sftp.mdx @@ -14,7 +14,7 @@ QueryPieでは、Webブラウザを通じて様々な作業を実行できるWeb ### Web SFTP画面構成
-![QueryPie Web > Servers > Terminal](/user-manual/server-access-control/using-web-sftp/image-20240802-061021.png) +QueryPie Web > Servers > Terminal
QueryPie Web > Servers > Terminal
@@ -27,7 +27,7 @@ QueryPie Web > Servers > Terminal ### Web SFTP機能の使用
-![image-20240723-160917.png](/user-manual/server-access-control/using-web-sftp/image-20240723-160917.png) +image-20240723-160917.png
1. パス表示窓：現在の位置が表示され、希望するパスを入力後`Enter`ボタンを押すと便利に移動できます。 @@ -46,7 +46,7 @@ QueryPie Web > Servers > Terminal ファイルアップロードおよびダウンロード時に以下のようなポップアップ窓を通じて転送状態および結果を確認できます。
-![image-20240802-061430.png](/user-manual/server-access-control/using-web-sftp/image-20240802-061430.png) +image-20240802-061430.png
1. **Name**：ディレクトリおよびファイルの名前が表示されます。 diff --git a/src/content/ja/user-manual/server-access-control/using-web-terminal.mdx b/src/content/ja/user-manual/server-access-control/using-web-terminal.mdx index 4846c9ee..8c9e30ed 100644 --- a/src/content/ja/user-manual/server-access-control/using-web-terminal.mdx +++ b/src/content/ja/user-manual/server-access-control/using-web-terminal.mdx @@ -14,7 +14,7 @@ QueryPieではウェブブラウザを通じてコマンドを実行できるウ ### ウェブターミナル画面構成
-![QueryPie Web > Servers > Terminal](/user-manual/server-access-control/using-web-terminal/image-20240802-060417.png) +QueryPie Web > Servers > Terminal
QueryPie Web > Servers > Terminal
@@ -33,7 +33,7 @@ QueryPie実験室では高性能ウェブターミナル機能を提供します ### 複数サーバー接続
-![QueryPie Web > Servers > Terminal](/user-manual/server-access-control/using-web-terminal/image-20240723-160622.png) +QueryPie Web > Servers > Terminal
QueryPie Web > Servers > Terminal
@@ -47,7 +47,7 @@ QueryPie Web > Servers > Terminal ### 複数セッション開く
-![Servers > Terminal > Open New Session](/user-manual/server-access-control/using-web-terminal/image-20240723-160649.png) +Servers > Terminal > Open New Session
Servers > Terminal > Open New Session
diff --git a/src/content/ja/user-manual/user-agent.mdx b/src/content/ja/user-manual/user-agent.mdx index 45d5ac31..b2222da0 100644 --- a/src/content/ja/user-manual/user-agent.mdx +++ b/src/content/ja/user-manual/user-agent.mdx @@ -16,7 +16,7 @@ QueryPie Agentをインストールすると、DataGrip、DBeaverのようなSQL 1. QueryPieログイン後右上プロフィールをクリックして`Agent Download`ボタンをクリックします。
-![QueryPie Web > プロフィールメニュー](/user-manual/user-agent/screenshot-20240804-173002.png) +QueryPie Web > プロフィールメニュー
QueryPie Web > プロフィールメニュー
@@ -25,7 +25,7 @@ QueryPie Web > プロフィールメニュー 2. QueryPie Agent Downloadsポップアップウィンドウが実行されるとStep 1で使用中のPCオペレーティングシステムに合うインストールファイルをダウンロードした後Step 3にあるQueryPie URLをコピーしておきます。
-![QueryPie Web > Agent Downloadsポップアップウィンドウ](/user-manual/user-agent/image-20240723-154847.png) +QueryPie Web > Agent Downloadsポップアップウィンドウ
QueryPie Web > Agent Downloadsポップアップウィンドウ
@@ -38,7 +38,7 @@ QueryPie AgentはMac、Windows、Linux OSをサポートします。 3. ダウンロードしたQueryPie Agentインストールプログラムを実行してインストールを完了します。
-![Mac OSインストールプログラム](/user-manual/user-agent/screenshot-20240804-174002.png) +Mac OSインストールプログラム
Mac OSインストールプログラム
@@ -48,7 +48,7 @@ Mac OSインストールプログラム QueryPie Host入力欄に事前にコピーしておいたQueryPie URLを入力して`Next`ボタンをクリックするとログイン画面にアクセスします。
-![Agent > QueryPie Host入力](/user-manual/user-agent/agent-03.png) +Agent > QueryPie Host入力
Agent > QueryPie Host入力
@@ -60,13 +60,13 @@ Agent > QueryPie Host入力 1. Agentアプリ内ログイン画面で`Login`ボタンをクリックします。
-![screenshot-20240804-173713.png](/user-manual/user-agent/screenshot-20240804-173713.png) +screenshot-20240804-173713.png
2. ウェブブラウザが開くと、ログインページで認証情報を入力し、`Continue`ボタンをクリックします。
-![QueryPie Web > Agent Login Page](/user-manual/user-agent/screenshot-20240729-171236.png) +QueryPie Web > Agent Login Page
QueryPie Web > Agent Login Page
@@ -75,7 +75,7 @@ QueryPie Web > Agent Login Page 3. ログインが成功すると下記のようにログイン成功画面が表示されその後Agentに戻ります。
-![QueryPie Web > Agent Login Success Page](/user-manual/user-agent/screenshot-20240729-171314.png) +QueryPie Web > Agent Login Success Page
QueryPie Web > Agent Login Success Page
@@ -84,7 +84,7 @@ QueryPie Web > Agent Login Success Page 4. Agent開きを明示的に実行して認証情報をAgentに伝達します。
-![Chrome - Agent App開きモーダル](/user-manual/user-agent/screenshot-20240804-174209.png) +Chrome - Agent App開きモーダル
Chrome - Agent App開きモーダル
@@ -95,7 +95,7 @@ Chrome - Agent App開きモーダル 1. ログインが正常に完了されるとAgentアプリ内Databasesタブで権限のあるコネクションの接続情報を確認できます。
接続するコネクションに割り当てられた`Port`をクリックすると、該当コネクションの`Proxy Credentials`情報を確認できます。
-![Agent > DB Connection Information](/user-manual/user-agent/screenshot-20240730-151001.png) +Agent > DB Connection Information
Agent > DB Connection Information
@@ -104,7 +104,7 @@ Agent > DB Connection Information 2. 上記の接続情報を3rd Partyクライアントに入力するとDBコネクション接続が可能です。
-![3rd Party Clientを利用したDBコネクション接続](/user-manual/user-agent/agent-07.png) +3rd Party Clientを利用したDBコネクション接続
3rd Party Clientを利用したDBコネクション接続
@@ -121,7 +121,7 @@ Agent > DB Connection Information * Default役割選択時、Workflow > Server Access Request要求により割り当てられたサーバー権限を使用します。
-![Agent > Server > Select a Role](/user-manual/user-agent/screenshot-20240730-162653.png) +Agent > Server > Select a Role
Agent > Server > Select a Role
@@ -136,7 +136,7 @@ Agent > Server > Select a Role * 接続するサーバーを右クリック後Open Connection withメニューを選択して、使用したいターミナルツールを選択します。
-![Agent > Server > Open Connection with](/user-manual/user-agent/screenshot-20240730-161729.png) +Agent > Server > Open Connection with
Agent > Server > Open Connection with
@@ -146,7 +146,7 @@ Agent > Server > Open Connection with * 使用したいアカウントを選択し必要時パスワードを入力した後、`OK`ボタンをクリックしてセッションを開きます。
-![Agent > Server > Open New Session](/user-manual/user-agent/screenshot-20240730-162532.png) +Agent > Server > Open New Session
Agent > Server > Open New Session
@@ -194,7 +194,7 @@ $ ssh deploy@{{Server Name}} ### エージェントを通じたKubernetes接続
-![kubernetes-agent-access-flow.png](/user-manual/user-agent/kubernetes-agent-access-flow.png) +kubernetes-agent-access-flow.png
* 権限を付与されたユーザーはエージェント実行時現在ポリシーに応じた`kubeconfig`ファイルが自動で受信されます。 @@ -208,7 +208,7 @@ $ ssh deploy@{{Server Name}} 希望する役割を選び`OK`ボタンをクリックしてください。
-![Agent > Kubernetes > Select a Role](/user-manual/user-agent/screenshot-20240730-152705.png) +Agent > Kubernetes > Select a Role
Agent > Kubernetes > Select a Role
@@ -225,7 +225,7 @@ Agent > Kubernetes > Select a Role 各クラスター右側の`🔍`ボタンを押すとPolicy Informationポップアップウィンドウが現れ、ここで該当クラスターに適用されたポリシー目録を詳しく確認できます。
-![Agent > Policy Information](/user-manual/user-agent/screenshot-20240730-161141.png) +Agent > Policy Information
Agent > Policy Information
@@ -236,7 +236,7 @@ Agent > Policy Information Agent設定メニューで`KubeConfig Path`ボタンをクリックしてKubeconfigパス設定モーダルを開きます。
-![Agent > Settings > Configure Kubeconfig Path](/user-manual/user-agent/screenshot-20240730-154623.png) +Agent > Settings > Configure Kubeconfig Path
Agent > Settings > Configure Kubeconfig Path
@@ -248,7 +248,7 @@ Agent > Settings > Configure Kubeconfig Path
-![パス指定ポップアップ](/user-manual/user-agent/screenshot-20240730-163530.png) +パス指定ポップアップ
パス指定ポップアップ
@@ -287,7 +287,7 @@ export KUBECONFIG="${KUBECONFIG}:${HOME}/.kube/querypie-kubeconfig" プロフィール領域右側`⚙️`ボタンをクリックして設定メニューを開きます。`Reset All Settings`ボタンをクリックします。
-![Agent > Settings](/user-manual/user-agent/screenshot-20240730-153518.png) +Agent > Settings
Agent > Settings
@@ -299,7 +299,7 @@ Agent > Settings メニューバーでQueryPie Agentアイコンをクリックしてアプリメニューを開きます。`Reset All Settings`ボタンをクリックします。
-![Agent > App menu](/user-manual/user-agent/screenshot-20240730-153524.png) +Agent > App menu
Agent > App menu
diff --git a/src/content/ja/user-manual/web-access-control.mdx b/src/content/ja/user-manual/web-access-control.mdx index 37ded3bb..8c7f0332 100644 --- a/src/content/ja/user-manual/web-access-control.mdx +++ b/src/content/ja/user-manual/web-access-control.mdx @@ -11,7 +11,7 @@ QueryPie WACはウェブアプリケーションに対するアクセスを制 ユーザーのすべてのウェブ活動をリアルタイムで追跡し記録して完全な可視性を提供します。
-![QueryPie Web > Web Access Control > Web Apps](/user-manual/web-access-control/image-20250629-151148.png) +QueryPie Web > Web Access Control > Web Apps
QueryPie Web > Web Access Control > Web Apps
diff --git a/src/content/ja/user-manual/web-access-control/accessing-web-applications-websites.mdx b/src/content/ja/user-manual/web-access-control/accessing-web-applications-websites.mdx index a2cf1092..fee49783 100644 --- a/src/content/ja/user-manual/web-access-control/accessing-web-applications-websites.mdx +++ b/src/content/ja/user-manual/web-access-control/accessing-web-applications-websites.mdx @@ -13,7 +13,7 @@ title: 'Webアプリケーション（Webサイト）への接続' ### Role選択
-![QueryPie Web > Web Access Control > Web Apps > Select a Role](/user-manual/web-access-control/accessing-web-applications-websites/image-20250629-151725.png) +QueryPie Web > Web Access Control > Web Apps > Select a Role
QueryPie Web > Web Access Control > Web Apps > Select a Role
@@ -26,7 +26,7 @@ QueryPie Web > Web Access Control > Web Apps > Select a Role ### Webアプリケーション（Webサイト）への接続
-![QueryPie Web > Web Access Control > Web Apps](/user-manual/web-access-control/accessing-web-applications-websites/image-20250629-152117.png) +QueryPie Web > Web Access Control > Web Apps
QueryPie Web > Web Access Control > Web Apps
diff --git a/src/content/ja/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx b/src/content/ja/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx index 6f3adfbb..74738bc4 100644 --- a/src/content/ja/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx +++ b/src/content/ja/user-manual/web-access-control/installing-root-ca-certificate-and-extension.mdx @@ -18,7 +18,7 @@ import { Callout } from 'nextra/components' 1. QueryPieにログインした状態で右上のプロフィールアイコンをクリックした後、Support > Download Web Secureメニューに移動します。
-![QueryPie > Profile Menu](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20241223-120321.png) +QueryPie > Profile Menu
QueryPie > Profile Menu
@@ -27,7 +27,7 @@ QueryPie > Profile Menu 1. QueryPie Web Secure Downloadモーダル窓が表示されたら、下記写真のようにA. Install Root CA Certificate項目のStep 1. Download Linkをクリックして証明書ファイルをダウンロードします。
-![QueryPie Web Secure Download](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20250116-155957.png) +QueryPie Web Secure Download
QueryPie Web Secure Download
@@ -46,7 +46,7 @@ QueryPie Web Secure Download * ダウンロードしたExtensionファイルを解凍しない状態のまま拡張機能ページ内にドラッグアンドドロップします。
-![Chrome > 拡張機能管理](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20241219-192626.png) +Chrome > 拡張機能管理
Chrome > 拡張機能管理
@@ -58,7 +58,7 @@ Chrome > 拡張機能管理 * Host情報が有効であれば`Go to Dashboard`ボタンが有効になります。このボタンをクリックすると新しいタブでQueryPieダッシュボードに移動します。
-![Host Configurationページ](/user-manual/web-access-control/installing-root-ca-certificate-and-extension/screenshot-20241219-192931.png) +Host Configurationページ
Host Configurationページ
diff --git a/src/content/ja/user-manual/workflow.mdx b/src/content/ja/user-manual/workflow.mdx index 784cecb1..37564d29 100644 --- a/src/content/ja/user-manual/workflow.mdx +++ b/src/content/ja/user-manual/workflow.mdx @@ -16,13 +16,13 @@ QueryPieを離れずに統合された環境で要求、承認、実行作業ま QueryPieはWorkflowメニューにアクセスする2つの経路を提供しています。
-![上部メニュー > General > Workflow](/user-manual/workflow/screenshot-20240902-172212.png) +上部メニュー > General > Workflow
上部メニュー > General > Workflow
-![My Dashboard > Workflow Requests](/user-manual/workflow/screenshot-20240725-145441.png) +My Dashboard > Workflow Requests
My Dashboard > Workflow Requests
@@ -88,7 +88,7 @@ Workflowメニュー内`Submit Request`ボタンを押した後、希望する 2. 処理したい要求をクリックして詳細内容を確認後右上で`Approve`または`Reject`をクリックします。
-![Workflow > Received Requests > To Do > List Details](/user-manual/workflow/image-20240801-062129.png) +Workflow > Received Requests > To Do > List Details
Workflow > Received Requests > To Do > List Details
@@ -111,7 +111,7 @@ A. DB Access Requestの場合一部DBコネクションに対してのみ部分 #### SQL Request実行
-![Workflow > Executions > To Do > List Details](/user-manual/workflow/screenshot-20240725-094850.png) +Workflow > Executions > To Do > List Details
Workflow > Executions > To Do > List Details
@@ -135,7 +135,7 @@ A. SQL Requestを通じて実行するクエリが大容量の場合、ウェブ #### SQL Export Request実行
-![Workflow > Executions > To Do](/user-manual/workflow/screenshot-20240725-104719.png) +Workflow > Executions > To Do
Workflow > Executions > To Do
diff --git a/src/content/ja/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx b/src/content/ja/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx index a5a58082..e4da323b 100644 --- a/src/content/ja/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx +++ b/src/content/ja/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc.mdx @@ -14,7 +14,7 @@ Workflow使用時に便利さを追加する付加機能をご紹介します。 ### 参照されたリクエストの確認処理
-![Workflow > Reviews > All Reviews > Review Details](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-114129.png) +Workflow > Reviews > All Reviews > Review Details
Workflow > Reviews > All Reviews > Review Details
@@ -37,7 +37,7 @@ Workflow > Reviews > All Reviews > Review Details #### 1. 代理決裁使用設定
-![User > 上部メニューバーでプロフィールクリック > Preferences](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-120401.png) +User > 上部メニューバーでプロフィールクリック > Preferences
User > 上部メニューバーでプロフィールクリック > Preferences
@@ -53,13 +53,13 @@ User > 上部メニューバーでプロフィールクリック > Prefere 代理決裁設定期間には元決裁者と代理決裁者のアクセス時に上部メニューバーに以下のように表示されます。
-![元決裁者基準表示内容](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-120741.png) +元決裁者基準表示内容
元決裁者基準表示内容
-![代理決裁者基準表示内容](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-120854.png) +代理決裁者基準表示内容
代理決裁者基準表示内容
@@ -77,7 +77,7 @@ User > 上部メニューバーでプロフィールクリック > Prefere * 詳細ページで承認または却下でき、Comment入力時には代理決裁中であることを知らせる文言が表示されます。
-![screenshot-20240802-124638.png](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240802-124638.png) +screenshot-20240802-124638.png
#### 4. 代理決裁処理されたリクエストの確認 @@ -85,14 +85,14 @@ User > 上部メニューバーでプロフィールクリック > Prefere * 以下のようにリクエスト詳細ページ内の承認状況で元決裁者または代理決裁者が処理したのかを確認できます。 **元決裁者が処理した場合**
-![代理決裁関連文言なし](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240725-153533.png) +代理決裁関連文言なし
代理決裁関連文言なし
**代理決裁者が処理した場合**
-![代理決裁者がDone by the delegateと共に表記される](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/screenshot-20240725-152141.png) +代理決裁者がDone by the delegateと共に表記される
代理決裁者がDone by the delegateと共に表記される
@@ -112,7 +112,7 @@ Slack DM通知関連の詳細は[Slack DM個人通知の使用](../../administra 同一内容で反復的な決裁リクエストをしたり、却下処理された決裁案件について以下のように再上申できます。
-![Workflow > Sent Requests > Done > List Details](/user-manual/workflow/approval-additional-features-proxy-approval-resubmission-etc/image-20230824-110815.png) +Workflow > Sent Requests > Done > List Details
Workflow > Sent Requests > Done > List Details
diff --git a/src/content/ja/user-manual/workflow/requesting-access-role.mdx b/src/content/ja/user-manual/workflow/requesting-access-role.mdx index e93724b4..fa81b3e9 100644 --- a/src/content/ja/user-manual/workflow/requesting-access-role.mdx +++ b/src/content/ja/user-manual/workflow/requesting-access-role.mdx @@ -22,7 +22,7 @@ Access Role Requestはアクセスが必要なサーバーまたはKubernetesク * ただし、Urgent Modeで申請する場合、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-access-role/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. 承認者の指定 @@ -34,7 +34,7 @@ Access Role Requestはアクセスが必要なサーバーまたはKubernetesク * **All Assignees must approve this request** : すべての承認者が承認して初めて承認要求が承認処理されます。
-![image-20240807-130021.png](/user-manual/workflow/requesting-access-role/image-20240807-130021.png) +image-20240807-130021.png
#### 3. 参照者の指定 @@ -45,7 +45,7 @@ Access Role Requestはアクセスが必要なサーバーまたはKubernetesク * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![image-20240807-130031.png](/user-manual/workflow/requesting-access-role/image-20240807-130031.png) +image-20240807-130031.png
#### 4. 事後承認で要求を送信 @@ -54,7 +54,7 @@ Access Role Requestはアクセスが必要なサーバーまたはKubernetesク * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![image-20240807-130043.png](/user-manual/workflow/requesting-access-role/image-20240807-130043.png) +image-20240807-130043.png
@@ -65,7 +65,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した #### 5. 要求対象役割（Role）の選択
-![QueryPie Web > Workflow > Submit Request > Access Role Request > Step 2](/user-manual/workflow/requesting-access-role/screenshot-20240802-111018.png) +QueryPie Web > Workflow > Submit Request > Access Role Request > Step 2
QueryPie Web > Workflow > Submit Request > Access Role Request > Step 2
@@ -83,7 +83,7 @@ Access Role Requestは一度に一つの役割のみ要求できます。
-![Screenshot-2025-08-26-at-1.18.14-AM.png](/user-manual/workflow/requesting-access-role/Screenshot-2025-08-26-at-1.18.14-AM.png) +Screenshot-2025-08-26-at-1.18.14-AM.png
1. **Role Expiration Date** : 該当権限が回収される有効期限を選択します。 @@ -93,7 +93,7 @@ Access Role Requestは一度に一つの役割のみ要求できます。 #### 6. 要求情報の入力
-![QueryPie Web > Workflow > Submit Request > Access Role Request > Step 3](/user-manual/workflow/requesting-access-role/Screenshot-2025-08-26-at-1.09.31-AM.png) +QueryPie Web > Workflow > Submit Request > Access Role Request > Step 3
QueryPie Web > Workflow > Submit Request > Access Role Request > Step 3
diff --git a/src/content/ja/user-manual/workflow/requesting-db-access.mdx b/src/content/ja/user-manual/workflow/requesting-db-access.mdx index cbfab21f..bce4212c 100644 --- a/src/content/ja/user-manual/workflow/requesting-db-access.mdx +++ b/src/content/ja/user-manual/workflow/requesting-db-access.mdx @@ -22,7 +22,7 @@ import { Callout } from 'nextra/components' * ただし、Urgent Modeで上申時、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.21.07-AM.png](/user-manual/workflow/requesting-db-access/Screenshot-2025-08-26-at-12.21.07-AM.png) +Screenshot-2025-08-26-at-12.21.07-AM.png
#### 2. 承認者指定 @@ -34,7 +34,7 @@ import { Callout } from 'nextra/components' * All Assignees must approve this request : すべての承認者が承認しなければ決裁要求が承認処理されます。
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-db-access/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. 参照者指定 @@ -45,7 +45,7 @@ import { Callout } from 'nextra/components' * `Save`ボタンを押してモーダルを閉じ参照者指定を完了します。
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-db-access/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. 事後承認で要求送信 @@ -58,7 +58,7 @@ import { Callout } from 'nextra/components' * Urgent mode = Onに設定後決裁要求を登録すると即座に権限を付与されたり作業を実行できます。
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-db-access/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -73,7 +73,7 @@ A. 管理者がUrgent Modeを許可しない決裁ルールを選択した場合 * **Reason for Request** : アクセス権限を要求する理由を入力します。
-![User > Workflow > Submit Request > DB Access Request > Request Summary](/user-manual/workflow/requesting-db-access/Screenshot-2025-08-26-at-12.24.44-AM.png) +User > Workflow > Submit Request > DB Access Request > Request Summary
User > Workflow > Submit Request > DB Access Request > Request Summary
@@ -87,13 +87,13 @@ User > Workflow > Submit Request > DB Access Request > Request Summa * **Expiration Date** : 現在該当コネクションに付与されている権限の期限切れ日を表示します。 * アクセス権限を要求するDBコネクションをチェックボックスで選択後下記二つの方法でPrivilege Typeを選択できます。
-![ドロップダウンを通じてコネクション別に指定](/user-manual/workflow/requesting-db-access/screenshot-20240801-191054.png) +ドロップダウンを通じてコネクション別に指定
ドロップダウンを通じてコネクション別に指定
-![チェックボックスおよびApplyボタンを通じた一括適用](/user-manual/workflow/requesting-db-access/screenshot-20240801-191152.png) +チェックボックスおよびApplyボタンを通じた一括適用
チェックボックスおよびApplyボタンを通じた一括適用
@@ -113,33 +113,33 @@ User > Workflow > Submit Request > DB Access Request > Request Summa 1. Submit Requestボタンを押し、メニューで「DB Access Request（Schema Level）」を選択します。
- ![image-20251218-120432.png](/user-manual/workflow/requesting-db-access/image-20251218-120432.png) + image-20251218-120432.png
2. `Add Item`ボタンを押します。
- ![image-20251218-120721.png](/user-manual/workflow/requesting-db-access/image-20251218-120721.png) + image-20251218-120721.png
3. 左側パネルで接続するコネクションを選択します。
- ![image-20251218-121011.png](/user-manual/workflow/requesting-db-access/image-20251218-121011.png) + image-20251218-121011.png
4. コネクションを選択すると右側のprivilege項目に基本的にselect権限が必要なスキーマに自動的にSELECT privilegeが付与されたことが見えます。この項目を削除することもできますが、その場合Web editorまたはproxyでスキーマ構造を照会する時点にエラーが発生する可能性があるため、やむを得ない場合でなければこの項目を削除しません。
`Add Item`ボタンを押します。
- ![image-20251218-121402.png](/user-manual/workflow/requesting-db-access/image-20251218-121402.png) + image-20251218-121402.png
5. 下に対象を追加できる行が追加されます。schema構造があるDBMS（Oracle、Postgresなど）は対象名を入力する時、必ず`{database名}`.`{schema名}`の形式で入力する必要があります。MySQLのようにschema構造がないDBMSは論理DB名のみ入力すれば 됩니다。
- ![image-20251218-122027.png](/user-manual/workflow/requesting-db-access/image-20251218-122027.png) + image-20251218-122027.png
* Oracle例：ORCLDB.TESTUSER * PostgreSQL例：testdb.test_schema * MySQL例：sakila
6. privilege割り当てはまずポップアップウィンドウ右側上部のHost Level Privilege項目で希望するprivilege typeを選択します。（スキーマレベルprivilegeはhost level privilegeの範囲内でのみ付与が可能なためです。例えばRead/WriteをHost Level Privilegeで選択した場合、その範囲内でSELECT、INSERTなどを付与できますが、Read-OnlyをHost Level Privilegeで選択した場合、SELECTのみ指定できます。）Host Level privilegeに割り当てが必要なprivilegeがない場合、管理者に該当コネクションに対して特定privilegeがあるprivilege typeを作成してほしいと要求する必要があります。
- ![image-20251218-122450.png](/user-manual/workflow/requesting-db-access/image-20251218-122450.png) + image-20251218-122450.png
7. 下に表示されるHost Level Others、Host Level Functionsは設定を見るだけです。Host LevelのPrivilegeの属性によりSchema Levelもprivilegeが従属するため、上位の情報を確認する用途で使用されます。
- ![image-20251218-122702.png](/user-manual/workflow/requesting-db-access/image-20251218-122702.png) + image-20251218-122702.png
8. `OK`ボタンを押し、フォームの残りの部分を入力した後`Submit`ボタンを押して要求を完了します。 diff --git a/src/content/ja/user-manual/workflow/requesting-db-policy-exception.mdx b/src/content/ja/user-manual/workflow/requesting-db-policy-exception.mdx index e9700f0d..0ef6b74c 100644 --- a/src/content/ja/user-manual/workflow/requesting-db-policy-exception.mdx +++ b/src/content/ja/user-manual/workflow/requesting-db-policy-exception.mdx @@ -21,7 +21,7 @@ import { Callout } from 'nextra/components' * ただし、Urgent Modeで申請する場合、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-db-policy-exception/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. 承認者の指定 @@ -33,7 +33,7 @@ import { Callout } from 'nextra/components' * All Assignees must approve this request : すべての承認者が承認して初めて承認要求が承認処理されます。
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-db-policy-exception/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. 参照者の指定 @@ -44,7 +44,7 @@ import { Callout } from 'nextra/components' * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-db-policy-exception/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. 事後承認で要求を送信 @@ -53,7 +53,7 @@ import { Callout } from 'nextra/components' * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-db-policy-exception/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -80,7 +80,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した * ページ下部の`Submit`ボタンを押して要求を申請します。
-![User > Workflow > Submit Request > DB Policy Exception Request](/user-manual/workflow/requesting-db-policy-exception/image-20251009-144630.png) +User > Workflow > Submit Request > DB Policy Exception Request
User > Workflow > Submit Request > DB Policy Exception Request
diff --git a/src/content/ja/user-manual/workflow/requesting-ip-registration.mdx b/src/content/ja/user-manual/workflow/requesting-ip-registration.mdx index 5ad4bd23..d539228e 100644 --- a/src/content/ja/user-manual/workflow/requesting-ip-registration.mdx +++ b/src/content/ja/user-manual/workflow/requesting-ip-registration.mdx @@ -21,7 +21,7 @@ import { Callout } from 'nextra/components' * **Approval Expiration Date** : 承認有効期限を入力します。Maximum Approval Durationを通じて最大値を設定できます。
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. 承認者の指定 @@ -33,7 +33,7 @@ import { Callout } from 'nextra/components' * **All Assignees must approve this request** : すべての承認者が承認して初めて承認要求が承認処理されます。
-![Screenshot-2025-06-26-at-3.56.29-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-3.56.29-PM.png) +Screenshot-2025-06-26-at-3.56.29-PM.png
#### 3. 参照者の指定 @@ -44,7 +44,7 @@ import { Callout } from 'nextra/components' * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![Screenshot-2025-06-26-at-3.57.36-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-3.57.36-PM.png) +Screenshot-2025-06-26-at-3.57.36-PM.png
@@ -54,7 +54,7 @@ import { Callout } from 'nextra/components' * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![Screenshot-2025-06-26-at-3.59.57-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-3.59.57-PM.png) +Screenshot-2025-06-26-at-3.59.57-PM.png
@@ -73,7 +73,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した * **Reason for Request (必須)** : IPアドレス登録を要求する理由を入力します。
-![Screenshot-2025-08-26-at-1.22.57-AM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-08-26-at-1.22.57-AM.png) +Screenshot-2025-08-26-at-1.22.57-AM.png
要求情報入力が完了したら、ページ下部の`Submit`ボタンを押して要求を申請します。 @@ -83,7 +83,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した 管理者によってIPアクセス制御政策（`Require Allowed Zones for User Access`）が有効化された状態で、許可リストにないIPでログインを試行する場合、ログインが遮断されIP登録のための専用ページに移動します。
-![Screenshot-2025-07-03-at-5.05.13-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-07-03-at-5.05.13-PM.png) +Screenshot-2025-07-03-at-5.05.13-PM.png
該当ページでは以下の手順に従ってIP登録を要求できます。 @@ -108,7 +108,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した 要求が正常に提出されると'Your IP request has been received.'案内メッセージと共に要求が正常に受付されたことを知らせる画面が表示されます。
-![Screenshot-2025-06-26-at-4.19.02-PM.png](/user-manual/workflow/requesting-ip-registration/Screenshot-2025-06-26-at-4.19.02-PM.png) +Screenshot-2025-06-26-at-4.19.02-PM.png
diff --git a/src/content/ja/user-manual/workflow/requesting-restricted-data-access.mdx b/src/content/ja/user-manual/workflow/requesting-restricted-data-access.mdx index 396838c9..574e259f 100644 --- a/src/content/ja/user-manual/workflow/requesting-restricted-data-access.mdx +++ b/src/content/ja/user-manual/workflow/requesting-restricted-data-access.mdx @@ -21,7 +21,7 @@ DACで「Data Access」政策によってアクセスが制限されたテーブ * ただし、Urgent Modeで申請する場合、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-restricted-data-access/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. 承認者の指定 @@ -33,7 +33,7 @@ DACで「Data Access」政策によってアクセスが制限されたテーブ * All Assignees must approve this request : すべての承認者が承認して初めて承認要求が承認処理されます。
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-restricted-data-access/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. 参照者の指定 @@ -44,7 +44,7 @@ DACで「Data Access」政策によってアクセスが制限されたテーブ * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-restricted-data-access/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. 事後承認で要求を送信 @@ -53,7 +53,7 @@ DACで「Data Access」政策によってアクセスが制限されたテーブ * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-restricted-data-access/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -79,7 +79,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した * ページ下部の`Submit`ボタンを押して要求を申請します。
-![User > Workflow > Submit Request > Restricted Data Access Request > Request Summary](/user-manual/workflow/requesting-restricted-data-access/image-20251009-140741.png) +User > Workflow > Submit Request > Restricted Data Access Request > Request Summary
User > Workflow > Submit Request > Restricted Data Access Request > Request Summary
diff --git a/src/content/ja/user-manual/workflow/requesting-server-access.mdx b/src/content/ja/user-manual/workflow/requesting-server-access.mdx index cd098294..33b2436d 100644 --- a/src/content/ja/user-manual/workflow/requesting-server-access.mdx +++ b/src/content/ja/user-manual/workflow/requesting-server-access.mdx @@ -22,7 +22,7 @@ Server Access Requestは承認即時に権限が付与され、ウェブター * ただし、Urgent Modeで申請する場合、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. 承認者の指定 @@ -34,7 +34,7 @@ Server Access Requestは承認即時に権限が付与され、ウェブター * All Assignees must approve this request : すべての承認者が承認して初めて承認要求が承認処理されます。
-![image-20240807-125743.png](/user-manual/workflow/requesting-server-access/image-20240807-125743.png) +image-20240807-125743.png
#### 3. 参照者の指定 @@ -45,7 +45,7 @@ Server Access Requestは承認即時に権限が付与され、ウェブター * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![screenshot-20240807-215819.png](/user-manual/workflow/requesting-server-access/screenshot-20240807-215819.png) +screenshot-20240807-215819.png
#### 4. 事後承認で要求を送信 @@ -54,7 +54,7 @@ Server Access Requestは承認即時に権限が付与され、ウェブター * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![image-20240807-125848.png](/user-manual/workflow/requesting-server-access/image-20240807-125848.png) +image-20240807-125848.png
@@ -65,7 +65,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した #### 5. 要求対象サーバーの追加
-![Workflow > Submit Request > Server Access Request > Step 2 > Add Servers](/user-manual/workflow/requesting-server-access/image-20240514-130023.png) +Workflow > Submit Request > Server Access Request > Step 2 > Add Servers
Workflow > Submit Request > Server Access Request > Step 2 > Add Servers
@@ -80,7 +80,7 @@ Workflow > Submit Request > Server Access Request > Step 2 > Add Ser ##### Require Minute-Based RequestsOnの場合
-![Screenshot-2025-08-26-at-1.05.08-AM.png](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-1.05.08-AM.png) +Screenshot-2025-08-26-at-1.05.08-AM.png
* **Start Trigger** : 権限付与開始条件を選択します。 @@ -91,7 +91,7 @@ Workflow > Submit Request > Server Access Request > Step 2 > Add Ser ##### Require Minute-Based RequestsOffの場合
-![Screenshot-2025-08-26-at-1.07.26-AM.png](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-1.07.26-AM.png) +Screenshot-2025-08-26-at-1.07.26-AM.png
* **Access Expiration Date** : 要求権限の有効期限を入力します。基本値は管理者ページのSAC configurations > Server Access Request Default SettingsのMaximum Access Duration値に従います。 @@ -105,7 +105,7 @@ Server Listテーブルにサーバーが追加されている状態でAdd Serve #### 6. 要求情報の入力
-![Workflow > Submit Request > Server Access Request > Step 3](/user-manual/workflow/requesting-server-access/Screenshot-2025-08-26-at-1.09.31-AM.png) +Workflow > Submit Request > Server Access Request > Step 3
Workflow > Submit Request > Server Access Request > Step 3
diff --git a/src/content/ja/user-manual/workflow/requesting-server-privilege.mdx b/src/content/ja/user-manual/workflow/requesting-server-privilege.mdx index baf02c58..9dee7c4a 100644 --- a/src/content/ja/user-manual/workflow/requesting-server-privilege.mdx +++ b/src/content/ja/user-manual/workflow/requesting-server-privilege.mdx @@ -22,7 +22,7 @@ Server Privilege Requestを使用すると、サーバーに対する一時的 * ただし、Urgent Modeで申請する場合、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. 承認者の指定 @@ -34,7 +34,7 @@ Server Privilege Requestを使用すると、サーバーに対する一時的 * **All Assignees must approve this request** : すべての承認者が承認して初めて承認要求が承認処理されます。
-![image-20240807-130021.png](/user-manual/workflow/requesting-server-privilege/image-20240807-130021.png) +image-20240807-130021.png
#### 3. 参照者の指定 @@ -45,7 +45,7 @@ Server Privilege Requestを使用すると、サーバーに対する一時的 * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![screenshot-20240807-215819.png](/user-manual/workflow/requesting-server-privilege/screenshot-20240807-215819.png) +screenshot-20240807-215819.png
#### 4. 事後承認で要求を送信 @@ -54,7 +54,7 @@ Server Privilege Requestを使用すると、サーバーに対する一時的 * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![image-20240807-125848.png](/user-manual/workflow/requesting-server-privilege/image-20240807-125848.png) +image-20240807-125848.png
@@ -69,7 +69,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した * ユーザーに付与されたRoleの中から一つを選択します。
-![image-20250307-123347.png](/user-manual/workflow/requesting-server-privilege/image-20250307-123347.png) +image-20250307-123347.png
#### 6. 要求対象サーバーの選択 @@ -79,7 +79,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した * `Add`ボタンをクリックしてモーダルを閉じ、サーバー選択を完了します。
-![image-20250307-123829.png](/user-manual/workflow/requesting-server-privilege/image-20250307-123829.png) +image-20250307-123829.png
#### 7. 使用するCommandsの入力 @@ -91,7 +91,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した * **Keyword** : コマンドをキーワードで入力できます。 * **RegEx** : コマンドを正規表現形式で入力できます。
- ![image-20250307-124234.png](/user-manual/workflow/requesting-server-privilege/image-20250307-124234.png) + image-20250307-124234.png
* Command Template選択時 @@ -99,7 +99,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した 1. ドロップダウンリストから使用する権限が含まれたテンプレートを選択します。 2. テンプレートを選択すると、含まれるコマンド（Keyword、RegEx）が画面に表示されますが、直接修正はできません。
- ![Screenshot-2025-07-22-at-3.43.34-PM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-07-22-at-3.43.34-PM.png) + Screenshot-2025-07-22-at-3.43.34-PM.png
@@ -119,7 +119,7 @@ A. 管理者がワークフローで使用するよう許可したテンプレ ##### Require Minute-Based RequestsOnの場合
-![Screenshot-2025-08-26-at-1.05.08-AM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-08-26-at-1.05.08-AM.png) +Screenshot-2025-08-26-at-1.05.08-AM.png
* **Start Trigger** : 権限付与開始条件を選択します。 @@ -130,7 +130,7 @@ A. 管理者がワークフローで使用するよう許可したテンプレ ##### Require Minute-Based RequestsOffの場合
-![Screenshot-2025-08-26-at-1.14.48-AM.png](/user-manual/workflow/requesting-server-privilege/Screenshot-2025-08-26-at-1.14.48-AM.png) +Screenshot-2025-08-26-at-1.14.48-AM.png
* **Privilege Expiration Date** : 要求権限の有効期限を入力します。基本値は管理者ページのSAC configurations > Server Privilege Request SettingsのMaximum Access Duration値に従います。 @@ -143,7 +143,7 @@ A. 管理者がワークフローで使用するよう許可したテンプレ * **Submit** : 要求をすべて作成したら`Submit`ボタンを押して申請を完了します。
-![image-20250307-124047.png](/user-manual/workflow/requesting-server-privilege/image-20250307-124047.png) +image-20250307-124047.png
diff --git a/src/content/ja/user-manual/workflow/requesting-sql-export.mdx b/src/content/ja/user-manual/workflow/requesting-sql-export.mdx index 9842bca8..e195dc39 100644 --- a/src/content/ja/user-manual/workflow/requesting-sql-export.mdx +++ b/src/content/ja/user-manual/workflow/requesting-sql-export.mdx @@ -22,7 +22,7 @@ import { Callout } from 'nextra/components' * ただし、Urgent Modeで申請する場合、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.43.46-AM.png](/user-manual/workflow/requesting-sql-export/Screenshot-2025-08-26-at-12.43.46-AM.png) +Screenshot-2025-08-26-at-12.43.46-AM.png
#### 2. 承認者の指定 @@ -34,7 +34,7 @@ import { Callout } from 'nextra/components' * **All Assignees must approve this request** : すべての承認者が承認して初めて承認要求が承認処理されます。
-![screenshot-20240807-215435.png](/user-manual/workflow/requesting-sql-export/screenshot-20240807-215435.png) +screenshot-20240807-215435.png
#### 3. 実行者と参照者の指定 @@ -45,7 +45,7 @@ import { Callout } from 'nextra/components' * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![screenshot-20240807-215506.png](/user-manual/workflow/requesting-sql-export/screenshot-20240807-215506.png) +screenshot-20240807-215506.png
#### 4. 事後承認で要求を送信 @@ -54,7 +54,7 @@ import { Callout } from 'nextra/components' * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![screenshot-20240807-215537.png](/user-manual/workflow/requesting-sql-export/screenshot-20240807-215537.png) +screenshot-20240807-215537.png
@@ -65,7 +65,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した #### 5. 要求情報の入力
-![User > Workflow > Submit Request > SQL Export Request > Request Summary](/user-manual/workflow/requesting-sql-export/Screenshot-2025-08-26-at-12.51.52-AM.png) +User > Workflow > Submit Request > SQL Export Request > Request Summary
User > Workflow > Submit Request > SQL Export Request > Request Summary
@@ -89,7 +89,7 @@ User > Workflow > Submit Request > SQL Export Request > Request Summ 承認が完了したExport Request件は承認完了と同時にダウンロード可能な状態になります。
-![screenshot-20240802-105329.png](/user-manual/workflow/requesting-sql-export/screenshot-20240802-105329.png) +screenshot-20240802-105329.png
1. Workflow > Executions > To Doメニューに移動します。 diff --git a/src/content/ja/user-manual/workflow/requesting-sql.mdx b/src/content/ja/user-manual/workflow/requesting-sql.mdx index fb14aa57..6d963cc0 100644 --- a/src/content/ja/user-manual/workflow/requesting-sql.mdx +++ b/src/content/ja/user-manual/workflow/requesting-sql.mdx @@ -22,7 +22,7 @@ import { Callout } from 'nextra/components' * ただし、Urgent Modeで上申時、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.43.46-AM.png](/user-manual/workflow/requesting-sql/Screenshot-2025-08-26-at-12.43.46-AM.png) +Screenshot-2025-08-26-at-12.43.46-AM.png
#### 2. 承認者指定 @@ -34,7 +34,7 @@ import { Callout } from 'nextra/components' * **All Assignees must approve this request** : すべての承認者が承認しなければ決裁要求が承認処理されます。
-![image-20240807-125031.png](/user-manual/workflow/requesting-sql/image-20240807-125031.png) +image-20240807-125031.png
#### 3. 実行者および参照者指定 @@ -45,7 +45,7 @@ import { Callout } from 'nextra/components' * `Save`ボタンを押してモーダルを閉じ参照者指定を完了します。
-![screenshot-20240807-215143.png](/user-manual/workflow/requesting-sql/screenshot-20240807-215143.png) +screenshot-20240807-215143.png
#### 4. 事後承認で要求送信 @@ -54,7 +54,7 @@ import { Callout } from 'nextra/components' * Urgent mode = Onに設定後決裁要求を登録すると即座に権限を付与されたり作業を実行できます。
-![screenshot-20240807-215226.png](/user-manual/workflow/requesting-sql/screenshot-20240807-215226.png) +screenshot-20240807-215226.png
@@ -65,7 +65,7 @@ A. 管理者がUrgent Modeを許可しない決裁ルールを選択した場合 #### 5. 要求情報入力
-![Screenshot-2025-08-26-at-12.47.02-AM.png](/user-manual/workflow/requesting-sql/Screenshot-2025-08-26-at-12.47.02-AM.png) +Screenshot-2025-08-26-at-12.47.02-AM.png
* **Title** : 要求タイトルを入力します。 @@ -85,7 +85,7 @@ A. 管理者がUrgent Modeを許可しない決裁ルールを選択した場合 承認が完了されたSQL Request件は承認完了即座に実行可能な状態になります。
-![Workflow > Executions > To Do > Request Details > Execute](/user-manual/workflow/requesting-sql/screenshot-20240802-104603.png) +Workflow > Executions > To Do > Request Details > Execute
Workflow > Executions > To Do > Request Details > Execute
@@ -105,7 +105,7 @@ DML Query実行に対する承認プロセスが強制された場合
`INSER この場合Web Editorでクエリ実行時下記のようなメッセージが出力されます。
`[ENGINE][30105] In this DML operation, you need to get approval throgh SQL Request.`
-![Web Editorで警告文](/user-manual/workflow/requesting-sql/image-20250629-155649.png) +Web Editorで警告文
Web Editorで警告文
@@ -115,7 +115,7 @@ Web Editorで警告文 DMLの場合Content TypeでFile添付方式で実行できません。
-![WorkflowのSQL Request様式](/user-manual/workflow/requesting-sql/image-20250629-161143.png) +WorkflowのSQL Request様式
WorkflowのSQL Request様式
diff --git a/src/content/ja/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx b/src/content/ja/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx index 773d30a4..f2d287ad 100644 --- a/src/content/ja/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx +++ b/src/content/ja/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature.mdx @@ -36,7 +36,7 @@ Content Typeは「Text」のみサポートします。
-![image-20241029-234721.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241029-234721.png) +image-20241029-234721.png
1. 実行計画（Explain）オプションおよび実行計画実行
クエリエディター下部にあるオプションを選択して`Explain`ボタンを押します。 @@ -46,31 +46,31 @@ Content Typeは「Text」のみサポートします。 2. **JSON** : JSON形式で結果が表示されます。
-![image-20241029-235845.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241029-235845.png) +image-20241029-235845.png
* 実行計画対象となるクエリ（セミコロンで終わる構文）は100個に制限されます。 * MySQLは5.6以降からExplainの結果をJSONフォーマットで出力できます。したがって5.6以前バージョンを対象にExplainを実行する場合、JSONで出力できません。
-![image-20241030-001252.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-001252.png) +image-20241030-001252.png
1. 実行計画（Explain）結果確認 1. Table形式の結果確認
以下の図のような結果が表示されます。各フィールドの意味はMySQL reference文書を参照してください。

- ![image-20241030-002325.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-002325.png) + image-20241030-002325.png
2. JSON形式の結果確認
JSONを選択してExplainボタンを押すと以下の図のような結果が表示されます。`{JSON}`をクリックすると全体JSON内容を確認できます。




エクスポート（Export）する時、管理者設定に応じてパスワード入力を要求するポップアップが出力される場合があります。
- ![`{JSON}`をクリックすると全体内容を見ることができます。](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-003040.png) + `{JSON}`をクリックすると全体内容を見ることができます。
`{JSON}`をクリックすると全体内容を見ることができます。
- ![JSON結果のコピーとエクスポートが可能です。](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-003129.png) + JSON結果のコピーとエクスポートが可能です。
JSON結果のコピーとエクスポートが可能です。
@@ -80,7 +80,7 @@ Content Typeは「Text」のみサポートします。 1. 承認者（Approver）の実行計画（Explain）結果確認
承認者はExplain Resultsタブで添付された実行計画（Explain）結果を確認し、承認の参考資料として活用できます。
- ![image-20241030-004258.png](/user-manual/workflow/requesting-sql/using-execution-plan-explain-feature/image-20241030-004258.png) + image-20241030-004258.png
diff --git a/src/content/ja/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx b/src/content/ja/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx index ae532d33..5796ca51 100644 --- a/src/content/ja/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx +++ b/src/content/ja/user-manual/workflow/requesting-unmasking-mask-removal-request.mdx @@ -21,7 +21,7 @@ DACでマスキング政策によってマスキングされた項目に対し * ただし、Urgent Modeで申請する場合、上記条件を無視します。
-![Screenshot-2025-08-26-at-12.54.02-AM.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/Screenshot-2025-08-26-at-12.54.02-AM.png) +Screenshot-2025-08-26-at-12.54.02-AM.png
#### 2. 承認者の指定 @@ -33,7 +33,7 @@ DACでマスキング政策によってマスキングされた項目に対し * All Assignees must approve this request : すべての承認者が承認して初めて承認要求が承認処理されます。
-![screenshot-20240724-154729.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/screenshot-20240724-154729.png) +screenshot-20240724-154729.png
#### 3. 参照者の指定 @@ -44,7 +44,7 @@ DACでマスキング政策によってマスキングされた項目に対し * `Save`ボタンを押してモーダルを閉じ、参照者指定を完了します。
-![screenshot-20240724-171350.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/screenshot-20240724-171350.png) +screenshot-20240724-171350.png
#### 4. 事後承認で要求を送信 @@ -53,7 +53,7 @@ DACでマスキング政策によってマスキングされた項目に対し * Urgent mode = Onに設定後、承認要求を登録すると即座に権限を付与されたり作業を実行できます。
-![screenshot-20240523-184245.png](/user-manual/workflow/requesting-unmasking-mask-removal-request/screenshot-20240523-184245.png) +screenshot-20240523-184245.png
@@ -78,7 +78,7 @@ A. 管理者がUrgent Modeを許可していない承認ルールを選択した * ページ下部の`Submit`ボタンを押して要求を申請します。
-![User > Workflow > Submit Request > Unmasking Request > Request Summary](/user-manual/workflow/requesting-unmasking-mask-removal-request/image-20251009-135940.png) +User > Workflow > Submit Request > Unmasking Request > Request Summary
User > Workflow > Submit Request > Unmasking Request > Request Summary