Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The KB already told you that it's an estimated value. It was used as a guideline for the system admin to set the MaxTokenSize registry key.</p> <pre><code>This formula uses the following values: d: The number of domain local groups a user is a member of plus the number of universal groups outside the user's account domain plus the number of groups represented in security ID (SID) history. s: The number of security global groups that a user is a member of plus the number of universal groups in a user's account domain. 1200: The estimated value for ticket overhead. This value can vary depending on factors such as DNS domain name length, client name, and other factors. In scenarios in which delegation is used (for example, when users authenticate to a domain controller), Microsoft recommends that you double the token size. </code></pre> <p>Why do you need to calculate the token size? Just want to make sure you didn't mix this up with process token.</p> <p>The token here means the Kerberos ticket or NTLM token which are normally cached and maintained by SSP. Since it's a very sensitive piece of information, it's highly protected and you normally cannot access it from your user mode application. The token the application normally deal with is the process token, which is different from the token described by this KB. However, it's true that the Kerberos ticket or NTLM token carries a lot of authorization information, which ultimately used to generate the process token. I don't recall there is a maximum token size limit on the process token. I might be wrong though.</p> <p>About the <em>SidHistory</em> question, I am not sure I get what you mean. Here is my understanding. The token contains a list of group SID, which may come from <em>SidHistory</em> from the AD group object. The token itself doesn't need to know whether the group SID is from <em>SidHistory</em> or <em>objectSid</em>. In case your application needs to look up the AD group object from the TOKEN_GROUPS information stored in the token, your application needs to do the query against <em>objectSid</em> as well as <em>sidHistory</em></p>
    singulars
    1. This table or related slice is empty.
    1. PODetermine the users TokenSize
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USHarvey Kwok
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COIt’s about the Kerberos token. We have reached, and partially exceeded the MaxTokenSize for some users since we began migrating to a new forest using SID-History. I need the user to run a script, showing him that he could potentially run into problems, and should contact support. I need as accurate a size as possible to keep the users working “trouble free” and not over stress the support. Is there a way, “just” to look at the users Token, to determine the size?
      singulars
      1. PO
      1. USDaro
    2. COI see. In that case, what I would suggest is that you can use [GetTokenInformation](http://msdn.microsoft.com/en-us/library/windows/desktop/aa446671%28v=vs.85%29.aspx) to get the TOKEN_GROUPS of your access token. Then, use [UserPrincipal](http://msdn.microsoft.com/en-us/library/system.directoryservices.accountmanagement.userprincipal.aspx) to find the group membership using LDAP. Compare the group lists. If there are any difference, then, your token is trimmed. Be careful to handle those built in group specially. I think this is the most reliable way.
      singulars
      1. PO
      1. USHarvey Kwok
    3. COI can’t figure out, how to get hold of TOKEN_GROUPS… and unfortunately the UserPrincipal’s „GetGroups()“ method does not retrieve the groups which SIDHhistory puts the user in.
      singulars
      1. PO
      1. USDaro
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload