Did you get any solution on this issue? I'm on 5.1.8 and facing the same problem.
Em segunda-feira, 8 de maio de 2017 23:27:42 UTC-3, Pedric Kng escreveu: > > Hi, > > I have enabled the SQL query statements to be printed and noticed that > quite a number of fields was missing from the auto create schema leading to > this error. > Can someone advise on this ? > > Hibernate: select abstractre0_.id as id2_0_, abstractre0_.access_strategy > as access_s3_0_, abstractre0_.attribute_release as attribut4_0_, > abstractre0_.description as descript5_0_, abstractre0_.evaluation_order as > evaluati6_0_, abstractre0_.informationUrl as informat7_0_, > abstractre0_.logo as logo8_0_, abstractre0_.logout_type as logout_t9_0_, > abstractre0_.logout_url as logout_10_0_, abstractre0_.mfa_policy as > mfa_pol11_0_, abstractre0_.name as name12_0_, abstractre0_.privacyUrl as > privacy13_0_, abstractre0_.proxy_policy as proxy_p14_0_, > abstractre0_.public_key as public_15_0_, abstractre0_.required_handlers as > require16_0_, abstractre0_.serviceId as service17_0_, abstractre0_.theme as > theme18_0_, abstractre0_.username_attr as usernam19_0_, > abstractre0_.bypassApprovalPrompt as bypassA20_0_, abstractre0_.clientId as > clientI21_0_, abstractre0_.clientSecret as clientS22_0_, > abstractre0_.generateRefreshToken as generat23_0_, abstractre0_.jsonFormat > as jsonFor24_0_, abstractre0_.supported_grants as support25_0_, > abstractre0_.supported_responses as support26_0_, > abstractre0_.DYNAMIC_REG_TIME as DYNAMIC27_0_, > abstractre0_.dynamicallyRegistered as dynamic28_0_, > abstractre0_.encryptIdToken as encrypt29_0_, > abstractre0_.idTokenEncryptionAlg as idToken30_0_, > abstractre0_.idTokenEncryptionEncoding as idToken31_0_, > abstractre0_.implicit as implici32_0_, abstractre0_.jwks as jwks33_0_, > abstractre0_.scopes as scopes34_0_, abstractre0_.signIdToken as > signIdT35_0_, abstractre0_.encryptAssertions as encrypt36_0_, > abstractre0_.metadataCriteriaDirection as metadat37_0_, > abstractre0_.metadataCriteriaPattern as metadat38_0_, > abstractre0_.metadataCriteriaRemoveEmptyEntitiesDescriptors as > metadat39_0_, abstractre0_.metadataCriteriaRemoveRolelessEntityDescriptors > as metadat40_0_, abstractre0_.metadataCriteriaRoles as metadat41_0_, > abstractre0_.metadataLocation as metadat42_0_, > abstractre0_.metadataMaxValidity as metadat43_0_, > abstractre0_.metadataSignatureLocation as metadat44_0_, > abstractre0_.nameIdQualifier as nameIdQ45_0_, > abstractre0_.requiredAuthenticationContextClass as require46_0_, > abstractre0_.requiredNameIdFormat as require47_0_, > abstractre0_.serviceProviderNameIdQualifier as service48_0_, > abstractre0_.signAssertions as signAss49_0_, abstractre0_.signResponses as > signRes50_0_, abstractre0_.expression_type as expressi1_0_ from > RegexRegisteredService abstractre0_ > 2017-05-09 10:16:07,962 ERROR > [org.hibernate.engine.jdbc.spi.SqlExceptionHelper] - <Invalid column name > 'bypassApprovalPrompt'.> > > > > On Monday, May 8, 2017 at 8:14:54 PM UTC+8, Pedric Kng wrote: >> >> hi, >> >> I am getting an invalid column name 'bypassApprovalPrompt' configuring MS >> SQL Service Registry with CAS-Management. >> >> Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid >> column name 'bypassApprovalPrompt'. >> >> This exception is thrown on 5.0.5 and 5.1.0-CR4, please advise. >> >> Thanks. >> >> Regards, >> Pedric >> > -- - Website: https://apereo.github.io/cas - Gitter Chatroom: https://gitter.im/apereo/cas - List Guidelines: https://goo.gl/1VRrw7 - Contributions: https://goo.gl/mh7qDG --- You received this message because you are subscribed to the Google Groups "CAS Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/apereo.org/d/msgid/cas-user/94a2566f-73de-4f23-851f-7ca3af8fbbee%40apereo.org.
