Abstract: Techniques for using signed nonces to secure cloud shells are provided. The techniques include receiving, by a session manager service, a request to connect a user device to a secure connection to a secure shell instance. The session manager service may authorize the user device to access the secure shell instance and may configure the secure shell instance, being described by a shell identifier of the secure shell instance. The techniques also include generating, by the session manager service, a nonce token and providing the shell identifier, and a router address of the secure shell router to the user device. The techniques also include generating, by the session manager service, a signed nonce token using the nonce token; and providing the signed nonce token and the shell identifier to a user device.

Abstract: The present embodiments relate to a cloud shell extension framework. A cloud infrastructure (CI) service can invoke a cloud shell from a console to the CI. The service may request that context data to be added for use in a terminal session. The cloud shell extension can include a tool or script that can be used to obtain context data or sample code for preparing an environment specific to the service prior to the user interaction with the environment. The cloud shell extension can allow for a service to register an extension in the cloud shell framework, and their extension can be invoked when a client initiates the cloud shell with the service. The extension can allow for the invoked service to forward context data, such as environment variables, to be set in the terminal session for the client.

Abstract: Techniques for using signed nonces to secure cloud shells are provided. The techniques include receiving, by a session manager service, a request to connect a user device to a secure connection to a secure shell instance. The session manager service may authorize the user device to access the secure shell instance and may configure the secure shell instance, being described by a shell identifier of the secure shell instance. The techniques also include generating, by the session manager service, a nonce token and providing the shell identifier, and a router address of the secure shell router to the user device. The techniques also include generating, by the session manager service, a signed nonce token using the nonce token; and providing the signed nonce token and the shell identifier to a user device.

Abstract: The present embodiments relate to a cloud shell extension framework. A cloud infrastructure (CI) service can invoke a cloud shell from a console to the CI. The service may request that context data to be added for use in a terminal session. The cloud shell extension can include a tool or script that can be used to obtain context data or sample code for preparing an environment specific to the service prior to the user interaction with the environment. The cloud shell extension can allow for a service to register an extension in the cloud shell framework, and their extension can be invoked when a client initiates the cloud shell with the service. The extension can allow for the invoked service to forward context data, such as environment variables, to be set in the terminal session for the client.

Abstract: Techniques for using signed nonces to secure cloud shells are provided. The techniques include receiving, by a session manager service, a request to connect a user device to a secure connection to a secure shell instance. The session manager service may authorize the user device to access the secure shell instance and may configure the secure shell instance, being described by a shell identifier of the secure shell instance. The techniques also include generating, by the session manager service, a nonce token and providing the shell identifier, and a router address of the secure shell router to the user device. The techniques also include generating, by the session manager service, a signed nonce token using the nonce token; and providing the signed nonce token and the shell identifier to a user device.

Abstract: The present embodiments relate to a cloud shell extension framework. A cloud infrastructure (CI) service can invoke a cloud shell from a console to the CI. The service may request that context data to be added for use in a terminal session. The cloud shell extension can include a tool or script that can be used to obtain context data or sample code for preparing an environment specific to the service prior to the user interaction with the environment. The cloud shell extension can allow for a service to register an extension in the cloud shell framework, and their extension can be invoked when a client initiates the cloud shell with the service. The extension can allow for the invoked service to forward context data, such as environment variables, to be set in the terminal session for the client.

Abstract: Techniques for using signed nonces to secure cloud shells are provided. The techniques include receiving, by a session manager service, a request to connect a user device to a secure connection to a secure shell instance. The session manager service may authorize the user device to access the secure shell instance and may configure the secure shell instance, being described by a shell identifier of the secure shell instance. The techniques also include generating, by the session manager service, a nonce token and providing the shell identifier, and a router address of the secure shell router to the user device. The techniques also include generating, by the session manager service, a signed nonce token using the nonce token; and providing the signed nonce token and the shell identifier to a user device.

Abstract: Techniques for using signed nonces to secure cloud shells are provided. The techniques include receiving, by a session manager service, a request to connect a user device to a secure connection to a secure shell instance. The session manager service may authorize the user device to access the secure shell instance and may configure the secure shell instance, being described by a shell identifier of the secure shell instance. The techniques also include generating, by the session manager service, a nonce token and providing the shell identifier, and a router address of the secure shell router to the user device. The techniques also include generating, by the session manager service, a signed nonce token using the nonce token; and providing the signed nonce token and the shell identifier to a user device.

Abstract: Techniques for using signed nonces to secure cloud shells are provided. The techniques include receiving, by a session manager service, a request to connect a user device to a secure connection to a secure shell instance. The session manager service may authorize the user device to access the secure shell instance and may configure the secure shell instance, being described by a shell identifier of the secure shell instance. The techniques also include generating, by the session manager service, a nonce token and providing the shell identifier, and a router address of the secure shell router to the user device. The techniques also include generating, by the session manager service, a signed nonce token using the nonce token; and providing the signed nonce token and the shell identifier to a user device.

Abstract: In accordance with an embodiment, described herein is a system and method for supporting a situational configuration in an application server environment includes at least one computer having an application server, enterprise, cloud computing, or other computing environment executing thereon, together with one or more managed server instances that operate as part of a domain and a situational configuration file defining server configuration setting changes and an expiration. The server configuration changes are loaded if the one or more managed server instances detect an addition of the situational configuration file or a change in the situational configuration file. The server configuration changes are unloaded if the one or more managed server instances detect deletion of the situational configuration or expiration of the situational configuration.

Abstract: In accordance with an embodiment, described herein is a system and method for supporting a situational configuration in an application server environment includes at least one computer having an application server, enterprise, cloud computing, or other computing environment executing thereon, together with one or more managed server instances that operate as part of a domain and a situational configuration file defining server configuration setting changes and an expiration. The server configuration changes are loaded if the one or more managed server instances detect an addition of the situational configuration file or a change in the situational configuration file. The server configuration changes are unloaded if the one or more managed server instances detect deletion of the situational configuration or expiration of the situational configuration.

Abstract: In accordance with an embodiment, a system and method provides a dynamic clustered messaging service in an application server environment. A cluster includes one or more servers operating within the application server environment and is configured to vary a number of the servers based on a service load of applications running on the cluster. The number also varies based on failure and restart of the servers. A messaging service for communicating messages between components of the applications includes instances of messaging service artifacts running on the one or more servers. A placement engine operating on the cluster is configured to migrate the instances of messaging service artifacts between the one or more servers based on a set of rules as the number of the one or more servers in the cluster expands and contracts and as a number of the instances of messaging service artifacts expands and contracts.

Abstract: In accordance with an embodiment, a system and method provides a dynamic clustered messaging service in an application server environment. A cluster includes one or more servers operating within the application server environment and is configured to vary a number of the servers based on a service load of applications running on the cluster. The number also varies based on failure and restart of the servers. A messaging service for communicating messages between components of the applications includes instances of messaging service artifacts running on the one or more servers. A placement engine operating on the cluster is configured to migrate the instances of messaging service artifacts between the one or more servers based on a set of rules as the number of the one or more servers in the cluster expands and contracts and as a number of the instances of messaging service artifacts expands and contracts.

Abstract: For a flexible error trace mechanism, embodiments may be implemented for C/C++ interface libraries, or in programs written in C/C++ or other programming languages. In one embodiment, when an error occurs in a function call, a trace element may be recorded that may include the source file name, function name, line number and other information that may be used to identify the error. In one embodiment, the library function may call a plurality of library functions in a function call stack. For each of the plurality of library functions, if the library function generates an error, an error trace element may be added to the error trace. After completion of the library function, the program may obtain the error trace for the library function. The error(s), if any, may be debugged using the information in the obtained error trace.

Abstract: A method, apparatus, and computer program product for managing and configuring program properties of an application program by loading properties from several lists, applying a set of precedence rules to resolve conflicts among properties, and applying the properties to the application program. Properties are listed in a plurality of lists including a list of default property values, a list of host-specific property values, a list of user-specific property values, a list of application-specific property values, and final properties lists. Values in the final property lists override conflicting previously loaded property values. The default properties list is loaded, as is a host-specific properties list, but only values for the then-current host are loaded. The user-specific properties list is loaded. User-defined properties override conflicting default properties.