IdPのサービス動作状況を確認する
以前構築したIdPにて、以下のURLで 404 Not Found エラーが発生する場合は、まず インストール（IdP） の virtualhost-localhost80.conf の設定を確認してください。
１．httpd と Jetty を再起動
IdPの設定変更後に各サービスの再起動を行っていない場合は、行ってください。
# systemctl stop jetty # systemctl restart httpd # systemctl start jetty
２．動作状況確認URLにアクセス
IdPサーバ自身から以下のようにアクセスして確認します。
# wget -O - http://localhost/idp/status
３．結果の確認
各サービスの動作状況が確認できます。以下のようにShibboleth IdPのバージョンを含めて各種情報が表示され、以下と比較して大きな違いがなければ、IdPの機能が正常に動作していることの確認が出来ました。
機能に問題がある場合は"last successful reload attempt:"の行が表示されないという場合もありますので、全ての機能(service)にこの行が存在して最近の日時であることを確認してください。
--2021-08-10 13:19:20-- http://localhost/idp/status
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 3021 (3.0K) [text/plain]
Saving to: 'STDOUT'
0% [ ] 0 --.-K/s ### Operating Environment Information
operating_system: Linux
operating_system_version: 3.10.0-1160.36.2.el7.x86_64
operating_system_architecture: amd64
jdk_version: 11.0.12
available_cores: 1
used_memory: 201 MB
maximum_memory: 1500 MB
### Identity Provider Information
idp_version: 4.1.2
start_time: 2021-08-10T02:29:02.499Z
current_time: 2021-08-10T04:19:20.805440Z
uptime: PT1H50M18.306S
enabled modules:
idp.authn.Duo (Duo Authentication)
idp.authn.External (External Authentication)
idp.authn.Function (Function Authentication)
idp.authn.IPAddress (IPAddress Authentication)
idp.authn.MFA (MFA Authentication)
idp.authn.Password (Password Authentication)
idp.authn.RemoteUser (RemoteUser Authentication)
idp.authn.RemoteUserInternal (RemoteUserInternal Authentication)
idp.authn.SPNEGO (SPNEGO Authentication)
idp.intercept.ContextCheck (Context Checking Interceptor)
idp.intercept.ExpiringPassword (Expiring Password Interceptor)
idp.intercept.Impersonate (Impersonation Interceptor)
idp.profile.CAS (CAS Protocol Suppport)
installed plugins:
service: shibboleth.LoggingService
last successful reload attempt: 2021-08-10T02:27:01.300846Z
last reload attempt: 2021-08-10T02:27:01.300846Z
service: shibboleth.AttributeFilterService
last successful reload attempt: 2021-08-10T04:12:13.814714Z
last reload attempt: 2021-08-10T04:12:13.814714Z
service: shibboleth.AttributeResolverService
last successful reload attempt: 2021-08-10T02:27:13.460500Z
last reload attempt: 2021-08-10T02:27:13.460500Z
No Data Connector has ever failed
service: shibboleth.AttributeRegistryService
last successful reload attempt: 2021-08-10T02:27:07.803095Z
last reload attempt: 2021-08-10T02:27:07.803095Z
service: shibboleth.NameIdentifierGenerationService
last successful reload attempt: 2021-08-10T02:27:15.220310Z
last reload attempt: 2021-08-10T02:27:15.220310Z
service: shibboleth.RelyingPartyResolverService
last successful reload attempt: 2021-08-10T02:27:15.538725Z
last reload attempt: 2021-08-10T02:27:15.538725Z
service: shibboleth.MetadataResolverService
last successful reload attempt: 2021-08-10T02:27:09.317461Z
last reload attempt: 2021-08-10T02:27:09.317461Z
metadata source: ShibbolethMetadata
last refresh attempt: 2021-08-10T02:27:09.825031Z
last successful refresh: 2021-08-10T02:27:09.825031Z
last update: 2021-08-10T02:27:09.825031Z
metadata source: LocalMetadata
last refresh attempt: 2021-08-10T02:27:09.825031Z
last successful refresh: 2021-08-10T02:27:09.825031Z
last update: 2021-08-10T02:27:09.825031Z
service: shibboleth.ReloadableAccessControlService
last successful reload attempt: 2021-08-10T02:27:16.532224Z
last reload attempt: 2021-08-10T02:27:16.532224Z
service: shibboleth.ReloadableCASServiceRegistry
last successful reload attempt: 2021-08-10T02:27:16.619707Z
last reload attempt: 2021-08-10T02:27:16.619707Z
service: shibboleth.ManagedBeanService
last successful reload attempt: 2021-08-10T02:27:16.721063Z
last reload attempt: 2021-08-10T02:27:16.721063Z
100%[======================================>] 3,021 --.-K/s in 0s
2021-08-10 13:19:20 (496 MB/s) - written to stdout [3021/3021]
