Devart Forums

I have downloaded dotConnect for PostgreSQL 5.50. The GSS implemention is still not working. I get a different error message this time. A token was invalid: unknown mech-code 0 for mech unknown"

The NpgSQL still works in my environment. Is there a test application or assembly logging you can provide to help trace into this issue? Is there anything I can turn on that would help pin-point the issue.

Have you tested it against the same environment that I mention I was using in this forum?

Thanks,

Charlie J.

Was this issue resolved in the release from yesterady? PostgreSQL 5.50


Thanks,

Charlie J.

Thanks. Very happy to help to get this implemented. We will test it in our environment as soon as it is available.

Thanks,

Charlie J. Biggs

Sorry. The issue is not in our environment. Npqsql works in our environment after my company submitted a patch to fix Npgsql. So if you are using there open source code for your implementation of GSSAPI, please make sure you get the code fix submitted by my company SSCS (Mike Kock) from there web site. I am sure the small changes that you said you implemented and will be in the next build will fix my problem I hope.

Please read the post to the PgFoundry about the fix to the Npgsql driver to get it to truly work with GSSAPI.

http://pgfoundry.org/forum/message.php?msg_id=1014589

Thanks,

Charlie J.

As I have mention certain times before, It works well with NpgSQL. We had to switch to NpgSQL because Devart did not support GSSAPI. It is not an issue with our environment. The issue is your dotConnect for Postgres does not support GSSAPI. The NpgSQL driver is Open Source, so you should be able to get an idea of how to implemented from reviewing what they did.

Thanks,

Charlie J.

Any update on the GSSAPI implementation? Can you send me a sample test application in case I am doing something wrong in my application?

Thanks,

Charlie J.

Any update on the GSSAPI implementation? Can you send my sample test application incase I am doing something wrong in my application?

Thanks,

Charlie J.

No. The GSSPI did not work. Here is the stack track

accepting GSS security context failedDescription: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: Devart.Data.PostgreSql.PgSqlException: accepting GSS security context failed

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:

[PgSqlException (0x80004005): accepting GSS security context failed] Devart.Data.PostgreSql.ag.af() +654 Devart.Data.PostgreSql.ag.a() +25 Devart.Common.DbConnectionFactory.a(DbConnectionBase A_0) +341 Devart.Common.DbConnectionClosed.Open(DbConnectionBase outerConnection) +145 Devart.Common.DbConnectionBase.Open() +216 Devart.Data.PostgreSql.PgSqlConnection.Open() +259 System.Data.EntityClient.EntityConnection.OpenStoreConnectionIf(Boolean openCondition, DbConnection storeConnectionToOpen, DbConnection originalConnection, String exceptionCode, String attemptedOperation, Boolean& closeStoreConnectionOnFailure) +52

Here is the Connection String in my web.config

connection string =


Postgres Server Log

Postgresql server log =
2011-08-24 10:35:28.341 PDTFATAL: accepting GSS security context failed
2011-08-24 10:35:28.341 PDTDETAIL: An unsupported mechanism was requested: unknown mech-code 0 for mech unknown

That would be Great. Thanks. Looking Forward to it.

Charlie J.

I am sure SSPI is working for Windows to Windows Authenication. I am doing Windows to FreeBSD (Postgres). It doesnt work for my scenario. NpgSQL works for both the SSPI and GSSPI case. Will there be support for GSSPI? SSPI is a proprietary variant of GSSAPI. The tokens generated and accepted by the SSPI are mostly compatible with the GSS-API so an SSPI client on Windows may be able to authenticate with a GSS-API server on UNIX depending on the specific circumstances.

Thanks,

Charlie J.

Any reply or update on my issues about SSPI/GSSPI?

Thanks,

Charlie J.

This did not work for me. I am using the latest dotConnection for Postgres 5.30.185 Postgres 9.x on a FreeBSD server. I am getting unsupported Authenication with I am using the Entity Developer to connect to my Database running on FreeBSD with integrated security = true. The Npgsql Provider supports SSPI/GSSPI.

It is easy to reproduce. Just install a Postgres 9.x on a FreeBSD Server and configure for Windows Authenciation and try to connect.

Thanks,

Charlie J.

Can I get a copy of the writing up? I am a current licensed user. You can send it to [email protected]

Thanks,

Charlie J.

I notice that SSPI Authenication Support was added in dotConnect for PostgreSQL 5.30.185. Does this support my case where I am using Entity Framework and DBProviderFactory in my web.config? Or do I still have to use only the coding method mention below

PgSqlConnection conn = new PgSqlConnection("Host=***;Port=***; Database=***;Integrated Security=True");
conn.Open();

Thanks,

Charlie J.

Yes. The problem is resolved by using the PgSQLEntityProviderServices in the constructor of the EF Context.

When will the UnpreparedExecute connection string parameter function the same way without put this workaround in the constructor of the EF Context?

Thanks,

Charlie J.