Delinea Web Password Filler 제작자: Delinea
Delinea’s web password manager backed by Delinea's flagship vaulting solution (Secret Server) for Privileged Access Management.
이 확장 기능을 사용하려면 Firefox가 필요함
확장 메타 데이터
스크린샷
정보
The Delinea Web Password Filler (WPF) browser extension manages credentials for web sites and web applications using Delinea's flagship vaulting solution to save, manage and autofill credentials. WPF can be used by customers that use the Delinea Platform, Delinea Secret Server Cloud or Delinea Secret Server on-premise vaults.
WPF supports enterprise single sign-on (SSO) using several mechanisms like Integrated Windows Authentication, SAML, and OpenID. It also supports MFA options such as the Delinea Mobile App, Duo, TOTP authenticator apps, email, FIDO2/YubiKey and others.
WPF goes beyond basic password management by seamlessly integrating with the Delinea vault’s advanced credential sharing workflows like approval-before-access, exclusive time-limited checkout/checkin access, MFA-on-access, etc. WPF can also be configured to record user-activity to meet audit and compliance needs.
Full Release Notes: https://docs.delinea.com/online-help/web-password-filler/release-notes/3.9.3.htm
WPF supports enterprise single sign-on (SSO) using several mechanisms like Integrated Windows Authentication, SAML, and OpenID. It also supports MFA options such as the Delinea Mobile App, Duo, TOTP authenticator apps, email, FIDO2/YubiKey and others.
WPF goes beyond basic password management by seamlessly integrating with the Delinea vault’s advanced credential sharing workflows like approval-before-access, exclusive time-limited checkout/checkin access, MFA-on-access, etc. WPF can also be configured to record user-activity to meet audit and compliance needs.
Full Release Notes: https://docs.delinea.com/online-help/web-password-filler/release-notes/3.9.3.htm
평가
권한더 알아보기
다음 권한 필요:
- Firefox 이외의 프로그램과 메시지 교환
- 최근 브라우징 기록, 쿠키, 관련 데이터 삭제
- 클립보드에 데이터 넣기
- 브라우저 탭에 접근
- 탐색 중 브라우저 활동에 접근
- 모든 웹사이트에서 사용자의 데이터에 접근
추가 정보
- 부가 기능 링크
- 버전
- 3.9.4
- 크기
- 762.39 KB
- 마지막 업데이트
- 3일 전 (2024년 6월 10일)
- 관련 카테고리
- 라이선스
- All Rights Reserved
- 개인정보처리방침
- 이 부가 기능에 대한 개인정보처리방침 읽기
- 사용자 라이선스 동의서
- 이 부가 기능에 대한 사용권 계약 읽기
- 버전 목록
- 태그
모음집에 추가
버전 3.9.4의 출시 정보
IMPROVEMENTS
* Due to new security restrictions in the latest versions of Safari, the browser can no longer differentiate between different types of connection errors. As a result, Web Password Filler now displays a more general error message: 'Unable to reach server. Verify that the server URL is correct, and that the server has a valid
certificate.' This message appears for both certificate and network issues.
* The caching of autofill matches have been removed. Web Password Filler now calls Secret Server every time it finds a login page. This change prevents issues where the system did not present new secrets to users for
autofill.
BUG FIXES
* A bug in the caching logic caused some secrets to not show up in the autofill match list.
* The refresh icon appeared in the popup if the user did not have the 'Add Secret' permission and no secrets were
present for that site.
* Web Password Filler would sometimes display the 'Add Secret' dialog in the wrong browser window when
adding a secret.
* When working in Mimecast, the Web Password Filler icon was displayed for some email fields, even though
those fields were not valid for autofill.
* https://sso.cloud.com would not autofill in Web Password Filler.
* Fixed an issue that caused visual corruption in some recorded sessions.
* When using the Web Password Filler popup window to generate a password, the generated password
contained duplicate letters. The passwords generated did not follow the Secret Server password policy.
* The system sometimes displayed 404 errors to the user when making background network calls to check the
validity of login URLs.
* Updated the autofill field detection logic to handle login forms in Italian.
*Web Password Filler did not close launched Chrome sessions upon secret check in or when the secret timeout
limit was reached.
* Web Password Filler reloaded the username page after the user submitted the username on some sites.
* An OTP API call occurred every 30 seconds, even if the user did not have the secret information page open.
* Due to new security restrictions in the latest versions of Safari, the browser can no longer differentiate between different types of connection errors. As a result, Web Password Filler now displays a more general error message: 'Unable to reach server. Verify that the server URL is correct, and that the server has a valid
certificate.' This message appears for both certificate and network issues.
* The caching of autofill matches have been removed. Web Password Filler now calls Secret Server every time it finds a login page. This change prevents issues where the system did not present new secrets to users for
autofill.
BUG FIXES
* A bug in the caching logic caused some secrets to not show up in the autofill match list.
* The refresh icon appeared in the popup if the user did not have the 'Add Secret' permission and no secrets were
present for that site.
* Web Password Filler would sometimes display the 'Add Secret' dialog in the wrong browser window when
adding a secret.
* When working in Mimecast, the Web Password Filler icon was displayed for some email fields, even though
those fields were not valid for autofill.
* https://sso.cloud.com would not autofill in Web Password Filler.
* Fixed an issue that caused visual corruption in some recorded sessions.
* When using the Web Password Filler popup window to generate a password, the generated password
contained duplicate letters. The passwords generated did not follow the Secret Server password policy.
* The system sometimes displayed 404 errors to the user when making background network calls to check the
validity of login URLs.
* Updated the autofill field detection logic to handle login forms in Italian.
*Web Password Filler did not close launched Chrome sessions upon secret check in or when the secret timeout
limit was reached.
* Web Password Filler reloaded the username page after the user submitted the username on some sites.
* An OTP API call occurred every 30 seconds, even if the user did not have the secret information page open.
Delinea 님의 다른 확장 기능
- 아직 평점이 없습니다
- 아직 평점이 없습니다
- 아직 평점이 없습니다
- 아직 평점이 없습니다
- 아직 평점이 없습니다
- 아직 평점이 없습니다