Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Get Started
- News & Events
- Collaboration
- Education Services
- Technologies
- Next-Generation Firewall
- GlobalProtect
- Threat Prevention Services
- Endpoint Protection
- 5G/IoT
- Prisma SD-WAN
Network Security
- Prisma Access
- Prisma Access Insights
- Prisma SaaS
- Prisma Cloud
- CN-Series
- VM-Series:
- Alibaba
- AWS
- GCP
- Azure
Cloud Security
- Cortex XDR
- Cortex XSOAR
- Cortex Data Lake
Security Operations
- Resources
- COVID-19 Response Center
- LIVEcommunity
- ›
- About OsramSecurity
About OsramSecurity
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
11-23-2020
1Post
0Likes
0Solutions
Nov 23, 2020Last Visited
User
Activity
User
Profile
Latest posts by OsramSecurity
| Subject | Views | Posted |
|---|---|---|
| 364 | 11-07-2012 01:44 PM |
User Badges
Public Statistics
| Date Registered | 09-09-2011 06:05 AM |
| Date Last Visited | 11-23-2020 07:52 AM |
| Total Messages Posted | 1 |
11-07-2012
01:44 PM
We have investigated the changes in version 4.1.8. and can share our findings: a) Administrator login now REQUIRES the domain field to be EMPTY b) User identification generally REQUIRES the domain field to be SET Until version 4.1.6. wit domain field set everything worked as expected, with 4.1.8. you need to create LDAP/Kerberos settings twice, one entry WITH and one W/O domain name. In addition Authentication sequence must be configured twice as well. Then for Admin accounts you select the Auth Profile with empty domains and for User identification (and possibly other purposes) you select the groups with domain fields set. Not nice but it works.
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
11-23-2020
07:52 AM
|
Latest Tags
No tags yet
Latest Blogs
Latest Posts
Copyright 2007 - 2021 - Palo Alto Networks
