digest | Provides a framework for message digest libraries | Hashing library

You have several issues here.

1. The second selectInput depends on the first one, so you need to update it also to display the updated dataframe.
2. It would be best to create a reactiveValues object as the dataframe to be updated.
3. You need an observeEvent to update the second selectInput, whenever the first one is updated.

Lastly, dataframe is updated only when the actionButton on the second tab is clicked - to avoid updating dataframe while typing long text.

Try this

Here I'm wondering about the line [in s_client]
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384

You're apparently using OpenSSL 1.0.2, where that's a basically useless relic. Back in the days when OpenSSL supported SSLv2 (mostly until 2010, although almost no one used it much after 2000), the ciphersuite values used for SSLv3 and up (including all TLS, but before 2014 OpenSSL didn't implement higher than TLS1.0) were structured differently than those used for SSLv2, so it was important to qualify the ciphersuite by the 'universe' it existed in. It has almost nothing to do with the protocol version actually used, which appears later in the session-param decode:

Ok, the signature container is embedded correctly.

But there are issues with the signature container itself:

• Both in the SignedData.digestAlgorithms collection and in the SignerInfo.digestAlgorithm value you have used the OID of SHA1withRSA, but that is a full signature algorithm, not the mere digest algorithm SHA1 expected there.

• Then the SHA1 hash of the signed bytes is BB78A402F7A537A34D6892B83881266501A691A8 but the hash you signed is 90E28B8A0D8E48691DAFE2BA10A4761FFFDCCD3D. This might be because you hash buffer2 and

  buffer2 has empty contents data (/Contents <>)

  The hex string delimiters '<' and '>' also belong to the contents value and, therefore, must also be removed in buffer2.

Furthermore, your signature is very weak:

• It uses SHA1 as hash algorithm. SHA1 meanwhile has been recognized as too weak a hash algorithm for document signatures.
• It doesn't use signed attributes, neither the ESS signing certificate nor the algorithm identifier protection attribute. Many validation policies require such special attributes.

Without using BigInteger:

They appear to be using an implementation of the http signatures draft.

The linked document explains the way the signature needs to be calculated and how to verify it. But this is probably why your example doesn't work:

2.1.3. headers

OPTIONAL. The headers parameter is used to specify the list of HTTP headers included when generating the signature for the message.

Basically the signature doesn't include just the message, probably to prevent replay attacks. Since you just hash the message it is working as intended.

The data is dynamically retrieved from an API call. You can retrieve direct from that url and simplify the json returned to get a dataframe:

You also need to import the database updates. Currently your auth server is trying to access tables and fields in your acore_auth database which don't exist.

https://www.azerothcore.org/wiki/database-keeping-the-server-up-to-date

tl;dr somewhere deep in the guts of the cli package (called to generate the pretty-printed output about column types), the code is generating a random string to use as a label.

A major clue is that

As Piotr P. Karwasz said it, I misspelled dataSourceName in context.xml and server.xml file. I feel bad that I didn't notice it.

But I still have one question : In which document should I put the realm tag ?