PHP 5는 지원이 종료되었으며 2026년 1월 31일에 지원 중단됩니다. 지원 중단 후에는 조직에서 이전에 조직 정책을 사용하여 레거시 런타임의 배포를 다시 사용 설정한 경우에도 PHP 5 애플리케이션을 배포할 수 없습니다. 기존 PHP 5 애플리케이션은 지원 중단 날짜 이후에도 계속 실행되고 트래픽을 수신합니다. 지원되는 최신 PHP 버전으로 마이그레이션하는 것이 좋습니다.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[[["\u003cp\u003eThe Users API allows developers to create URLs for user sign-in and sign-out actions, redirecting them back to the application afterward.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eUserService::createLoginUrl()\u003c/code\u003e and \u003ccode\u003eUserService::createLogoutUrl()\u003c/code\u003e functions generate the URLs for signing in and out, respectively, while requiring a destination URL for redirection.\u003c/p\u003e\n"],["\u003cp\u003eThe development web server simulates Google Accounts with its sign-in/sign-out mechanisms, prompting for an email address when signing in locally.\u003c/p\u003e\n"],["\u003cp\u003eAccess to specific parts of an application can be restricted to signed-in users using the \u003ccode\u003elogin: required\u003c/code\u003e configuration element for URL handlers.\u003c/p\u003e\n"],["\u003cp\u003eThis API is specific to first-generation runtimes in the App Engine standard environment and has different options in later versions.\u003c/p\u003e\n"]]],[],null,["# Login URLs\n\nThe Users API provides functions for constructing URLs that allow the user to sign in or sign out, then be redirected back to your application.\n| This page describes how to use the legacy bundled services and APIs. This API can only run in first-generation runtimes in the App Engine standard environment. If you are updating to the App Engine PHP 7/8 runtime, refer to the [migration guide](/appengine/migration-center/standard/migrate-to-second-gen/php-differences) to learn about your migration options for legacy bundled services.\n\n`UserService::createLoginUrl()` and `UserService::createLogoutUrl()` each take a destination URL for the application, and return a URL for signing in or signing out that redirects back to the given URL afterward. \n\n```php\nuse google\\appengine\\api\\users\\User;\nuse google\\appengine\\api\\users\\UserService;\n\n$user = UserService::getCurrentUser();\nif (isset($user)) {\n echo sprintf('Welcome, %s! (\u003ca href=\"%s\"\u003esign out\u003c/a\u003e)',\n $user-\u003egetNickname(),\n UserService::createLogoutUrl('/'));\n} else {\n echo sprintf('\u003ca href=\"%s\"\u003eSign in or register\u003c/a\u003e',\n UserService::createLoginUrl('/'));\n}\n```\n\nThe development web server simulates Google Accounts using its own sign-in and sign-out facilities. When you sign in to your application on the development web server, the server prompts you for an email address to use for the session. See [The Development Web Server](/appengine/docs/legacy/standard/php/tools/using-local-server) for more information.\n\n**Tip:** An easy way to restrict access to a part of your application to signed in users is to use the `login: required` configuration element for the URL handler. See [Configuring an App](/appengine/docs/legacy/standard/php/config/appref)."]]
