New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WFCORE-820] Attribute for-hosts for Security Realm with Kerberos doe… #887
Conversation
Windows Build 1706 is now running using a merge of b26cecd |
Core - Full Integration Build 1314 is now running using a merge of b26cecd |
Linux Build 2178 is now running using a merge of b26cecd |
Windows Build 1706 outcome was SUCCESS using a merge of b26cecd |
Core - Full Integration Build 1314 outcome was FAILURE using a merge of b26cecd Build problems:Failed tests detected Failed tests
|
Linux Build 2178 outcome was FAILURE using a merge of b26cecd Build problems:Execution timeout |
Retest this please. |
Core - Full Integration Build 1315 is now running using a merge of b26cecd |
Windows Build 1707 is now running using a merge of b26cecd |
Linux Build 2179 is now running using a merge of b26cecd |
Windows Build 1707 outcome was SUCCESS using a merge of b26cecd |
Linux Build 2179 outcome was SUCCESS using a merge of b26cecd |
Core - Full Integration Build 1315 outcome was FAILURE using a merge of b26cecd Build problems:Failed tests detected Failed tests
|
2 - Iterate the list of keytabs and identity one where the for-hosts attribute contains an entry matching hostname. | ||
3 - Iterate the list of keytabs and identify one where the name of the principal matches matches protocol/hostname. | ||
2 - Iterate the list of keytabs and identify one where the name of the principal matches matches protocol/hostname. | ||
3 - Iterate the list of keytabs and identity one where the for-hosts attribute contains an entry matching hostname. | ||
4 - Iterate the list of keytabs and identify one where the hostname portion of the principal matches the hostname of the request. | ||
5 - Use the keytab where for-hosts is set to '*'. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a9c2d7a
to
15796e6
Compare
Linux Build 2184 is now running using a merge of 15796e6 |
Windows Build 1711 is now running using a merge of 15796e6 |
Core - Full Integration Build 1321 is now running using a merge of 15796e6 |
Ah, thanks Brian. Didn't realize there may be newer version. So probably only fix the latest one...? Can I actually change XSD documentation just like that? Should I involve documentation team for some reason? |
Windows Build 1711 outcome was SUCCESS using a merge of 15796e6 |
Linux Build 2184 outcome was SUCCESS using a merge of 15796e6 |
Core - Full Integration Build 1321 outcome was SUCCESS using a merge of 15796e6 |
…s not select keytab in defined order
Windows Build 1717 is now running using a merge of b71540b |
Core - Full Integration Build 1327 is now running using a merge of b71540b |
Linux Build 2190 is now running using a merge of b71540b |
Windows Build 1717 outcome was SUCCESS using a merge of b71540b |
Linux Build 2190 outcome was SUCCESS using a merge of b71540b |
Core - Full Integration Build 1327 outcome was FAILURE using a merge of b71540b Build problems:Failed tests detected Failed tests
|
Hi Tomas, Sorry, I didn't check back to see your comment. Generally we don't update schemas once they are published in a final release. It's confusing to have different variations of the same schema out there on the internet. So just the latest is ok. If you need to fix BZ 1228228 (currently it's not triaged for inclusion in a CP and I doubt it ever will be) and someone insists on updating the 1.7 schema as the fix, we won't object to changing it in WildFly Core as well. Re: docs, probably the simplest thing to do is change the "Doc Type" on the BZ to Known Issue and fill in the Doc Text. I believe that will provide the info needed to create an entry in the EAP Release Notes if docs wants one. |
retest this please |
Windows Build 1767 is now running using a merge of b71540b |
Linux Build 2242 is now running using a merge of b71540b |
Core - Full Integration Build 1378 is now running using a merge of b71540b |
Windows Build 1767 outcome was SUCCESS using a merge of b71540b |
Linux Build 2242 outcome was SUCCESS using a merge of b71540b |
Core - Full Integration Build 1378 outcome was FAILURE using a merge of b71540b Build problems:Failed tests detected Failed tests
|
[WFCORE-820] Attribute for-hosts for Security Realm with Kerberos doe…
[WFCORE-4690] Fix the test suite tests to work with Eclipse OpenJ9.
…s not select keytab in defined order
https://bugzilla.redhat.com/show_bug.cgi?id=1228228
https://issues.jboss.org/browse/WFCORE-820